Interactions: stateless replay of an `mcp_server_tool_result` whose `structured_content` holds a `$ref` returns 400

オープン
  • 何か問題がありますか？
#3,313 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
57/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
python
領域
api

調査の方向性

Start by tracing how the SDK models and serializes mcp_server_tool_result steps for stateless Interactions API requests; the issue does not name specific files or tests. Compare the returned structured_content reference with the replayed function response, then add a regression test using the reproduction shape. Done means replaying the emitted steps succeeds when structured_content contains a $ref.

索引モデルが issue の本文から書いたものです。

説明

This issue was posted by Claude Code using claude-opus-5-5 on behalf of David.

Interactions API rejects its own mcp_server_tool_result step on stateless replay when structured_content contains a $ref.

With store: false, sending back the steps a previous interaction returned fails with HTTP 400 when an MCP image result came from a server that also sets structuredContent:

400 {"error":{"message":"The referenced name `structured_content.result[0]` in function_response.response does not match to a display_name in the function_response.parts.","code":"invalid_request"}}

The step is exactly what the API emitted. Image results without structured_content, and audio and embedded-resource results, replay fine (200).

Reproduce (raw HTTP, no SDK)

  1. Run a public MCP server with a tool returning an ImageContent block and matching structuredContent. FastMCP does this for a tool annotated -> list[ImageContent]:

    from mcp.server.fastmcp import FastMCP
from mcp.types import ImageContent

PNG = 'iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVR4nGNg+M/A8B8ABf4C/gzLSmsAAAAASUVORK5CYII='
mcp = FastMCP('probe', stateless_http=True)

@mcp.tool()
def get_image() -> list[ImageContent]:
    return [ImageContent(type='image', data=PNG, mimeType='image/png')]

mcp.run(transport='streamable-http')

  2. POST /v1beta/interactions with model: gemini-3.8-flash, store: false, tools: [{"type": "mcp_server", "name": "probe", "url": "<server>/mcp"}], and a user_input asking it to call get_image. The response contains:

    {"type": "mcp_server_tool_result", "call_id": "...", "signature": "...", "name": "probe:get_image", "server_name": "probe",
 "result": {"call_tool_result_json": "{\"content\":[{\"type\":\"image\",...}],\"structuredContent\":{...}}",
            "structured_content": {"result": [{"$ref": "structured_content.result[0]"}]}}}

  3. Send a second request whose input is the first user_input, every returned step unchanged, and a new user_input. It returns the 400 above. Dropping only that tool's call and result steps returns 200.

Related: the live result shape differs from the reference and SDK types
  • The API reference documents mcp_server_tool_result.result as (ImageContent or TextContent) array, object or string. Live results for text, image, audio and embedded-resource tools all arrive as an undocumented object: call_tool_result_json (the MCP CallToolResult as a JSON string), optional structured_content, a plain-text result, and for blob resources a key named after the MIME type ("application/pdf": "<base64>").
  • MCPServerToolResultStepResult in this SDK is an empty model, so none of those fields are typed. The list branch types only text and image items; audio, video and document items parse as UnknownFunctionResultSubcontent.

Observed with google-genai 2.30.0 on the Gemini API (gemini-3.8-flash), November 2026.

主要言語
Python
スター
4.1k
フォーク
1.1k
平均マージ
1日 21時間
マージ済み PR（30日）
103

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

googleapis/python-genai のほかの issue

googleapis/python-genai の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。