Skip to main content
Glama
alexdlaird

amazon-orders-mcp

by alexdlaird
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_family_members

Read-only

Lists Amazon household or family members for a specified site. Deprecated: use get_orders with household_members instead.

Instructions

Deprecated, use get_orders, whose household_members lists the same members.

Input Schema

NameRequiredDescriptionDefault
siteNoThe Amazon site to read, e.g. `amazon.de`, since each site has its own orders. By default, the user's default site (see `check_session`).

Output Schema

NameRequiredDescriptionDefault
itemsNoThe FamilyMembers, or an empty list if the account has none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.2
    • removedInput schema / properties / site / title
      Removed value: -"Site"
  2. Changed1 schema field changedv2.1.0
    • changedOutput schema / properties / items / items / properties / id / description
      Previous value: -"The FamilyMember ID, Amazon's `familyMemberId`."New value: +"The FamilyMember ID, the value Amazon's household member filter (`householdMembers`) takes."
  3. Changed1 schema field changedv2.0.1
    • changedOutput schema / properties / items / items / description
      Previous value: -"A member of the Amazon Household whose Orders the account can view, such as a linked Teen account. Pass its `id` as `family_member_id` to `get_order_history` to get their Orders."New value: +"A member of the Amazon Household whose Orders the account can view, such as a linked Teen account. Pass its `id` as `family_member_id` to `get_orders` to get their Orders."
  4. Addedv1.4.2

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds the genuinely useful behavioral fact that the tool is deprecated, but it does not say whether calls still succeed, when removal happens, or what happens if an agent uses it anyway. It also adds nothing about the per-site read behavior beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, deprecation notice front-loaded, and the actionable replacement immediately follows. Nothing extraneous.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a deprecated read-only tool with a single documented parameter and an output schema, the description supplies everything an agent needs to make the routing decision. The only missing piece is whether the tool still functions at all, which would matter if an agent is forced to fall back to it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single `site` parameter is fully documented in the schema, including the default-site fallback. The description adds no parameter guidance, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource indirectly through the replacement's field ('household_members lists the same members'), making clear this tool returns family/household members, and it explicitly distinguishes itself from the sibling get_orders. It never states the verb directly ('lists family members'), so the purpose is inferred rather than declared.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit do-not-use instruction plus the exact alternative (`get_orders`) and the specific field that covers the same need (`household_members`). An agent has no ambiguity about which tool to call.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools