Response syntax includes agentVersion but it's missing in the actual HTTP response

[raquelfmcardoso]

Describe the issue

Hi boto3 maintainers,

While using AgentsforBedrock, I noticed a discrepancy in the documentation:

The response syntax for the following methods includes the field agentVersion, but the field does not appear in the actual HTTP response:

• create_agent
• update_agent
• get_agent

This can be reproduced by calling any of these operations and inspecting the raw HTTP response.

Environment details:

• Python: 3.13.7
• boto3: 1.40.19

It would be great if the agentVersion field was actually included in the response, since it would make working with agents more convenient. That said, I understand this may be low priority, as it’s possible to retrieve agent versions using list_agent_versions. Therefore, I'm suggesting a documentation fix instead of a feature request, as resolving this discrepancy would improve clarity for users.

Thanks for maintaining this library and for all your hard work!

Links

• Create Agent
• Update Agent
• Get Agent

[RyanFitzSimmonsAK]

Hi @raquelfmcardoso, thanks for reaching out. agentVersion is documented as part of the response because it shares the same agent structure (https://docs.aws.amazon.com/bedrock/latest/APIReference/API_agent_Agent.html). This is a common nuance of AWS documentation. When a structure is reused across multiple operations, the request and response syntax will show every possible parameter of that structure. However, not every operation accepts or returns every possible parameter of that structure, and you often need to reference an example to get more information. In this case, there's not a way to correctly document this, so the best solution is probably a feature request for these operations to include agentVersion in the response. If you'd like, I'd be happy to forward this feedback to the service team.

[github-actions]

Greetings! It looks like this issue hasn’t been active in longer than five days. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.