Skip to main content
Glama

Sync eBay shipping policies

sync_ebay_fulfillment_policies
Read-only

Re-read the eBay shipping (fulfillment) policies from eBay for every site the connection sells on, or one marketplaceId, and refresh the copy the CRM keeps — after the seller created, renamed or deleted a policy in Seller Hub. Returns the same shape as list_ebay_fulfillment_policies; check staleAssignments: products whose chosen policy eBay no longer has will be refused at their next draft or go-live until another policy is chosen. Changes no listing and no choice. Use list_ebay_fulfillment_policies for an ordinary read.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sync_ebay_fulfillment_policies"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketplaceIdNoAn eBay MARKETPLACE id such as EBAY_IT. Omit it to refresh every marketplace the eBay connection sells on.

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?

Goes well beyond the annotations: it discloses the returned shape, the staleAssignments warning field and its downstream consequence (products refused at next draft or go-live), and explicitly bounds the mutation ('Changes no listing and no choice'), which reconciles the refresh-the-CRM-copy behavior with readOnlyHint=true.

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?

Front-loaded with the action and scope, and every sentence carries information. The staleAssignments sentence is dense and slightly convoluted, but nothing is filler.

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?

There is no output schema, but the description supplies the return-shape contract by reference to list_ebay_fulfillment_policies plus the one extra field that matters (staleAssignments). Given one optional param and a clear safety profile, an agent has everything needed to call it correctly.

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% and the single marketplaceId enum is fully documented in the schema, including the omit-to-refresh-all semantics. The description echoes this ('or one marketplaceId') without adding new syntax or format detail, so it sits at the high-coverage baseline.

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 precise verb+resource ('Re-read the eBay shipping (fulfillment) policies ... and refresh the copy the CRM keeps') with scope (every site the connection sells on, or one marketplaceId). It explicitly distinguishes itself from the sibling list_ebay_fulfillment_policies, which is a plain read.

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?

Gives the triggering condition ('after the seller created, renamed or deleted a policy in Seller Hub') and names the alternative and when to prefer it ('Use list_ebay_fulfillment_policies for an ordinary read'). An agent can route without guessing.

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