Skip to main content
Glama

Get eBay offer policies

get_ebay_offer_policies
Read-only

Read the eBay offers of up to 25 products live and return, per offer, the fulfillment, payment and return policy ids it carries now, the shipping policy name, its eBay site and status (PUBLISHED = live, UNPUBLISHED = draft), and matchesAssignment — whether it carries the product's own choice in the CRM (null when the product has none). Products with no draft or live listing are listed in withoutOffer; notAttempted were not reached in the time budget — call again with those ids. Reads only. Use get_product_ebay_fulfillment_policy for one product's full picture.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "productIds": "<productIds>"
    },
    "name": "get_ebay_offer_policies"
  }
}

Input Schema

NameRequiredDescriptionDefault
productIdsYesThe products whose eBay offers to read, at most 25 ids from search_products.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark it read-only/non-destructive, and the description reinforces that ('Reads only') while adding behavior the annotations cannot convey: the meaning of PUBLISHED vs UNPUBLISHED, matchesAssignment null semantics, the withoutOffer bucket, and partial results bounded by a time budget with a retry instruction. This is genuine disclosure beyond the safety profile.

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

Conciseness4/5

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

A single dense paragraph that is front-loaded with the core action and result shape, with no filler sentences. It is slightly overloaded by stacking status semantics, matchesAssignment, withoutOffer, and notAttempted into one run-on flow, but every clause still carries meaning.

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

Completeness5/5

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

With no output schema, the description carries the return-value burden and does so by describing the per-offer payload and both result buckets. For a one-parameter read tool, an agent has everything needed to call it and interpret partial results.

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 description coverage is 100% for the single productIds parameter, so the schema already documents the array source, min/max items, and id origin. The description only restates the 25 cap and the search_products origin, adding no syntax or format detail. Baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource (read the eBay offers of up to 25 products live) and enumerates exactly what comes back per offer: fulfillment/payment/return policy ids, shipping policy name, site, status, and matchesAssignment. It also explicitly contrasts with the sibling get_product_ebay_fulfillment_policy, so an agent can distinguish the two without opening schemas.

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?

Names the alternative tool (get_product_ebay_fulfillment_policy) for a single product's full picture, and gives an explicit recovery path for unresolved products (call again with the notAttempted ids). Both the 'when' and the 'what next' are spelled out.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources