Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Amazon Shop page

amazon_shop_get
Read-onlyIdempotent

Fetch a creator’s Amazon Shop storefront by public URL to view its details; use the returned cursor for pagination.

Instructions

Get a creator Amazon Shop storefront by URL. Requires url. Send only url, plus cursor from a previous response. Leave unused fields out instead of sending null.

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": {
      "url": "<url>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "amazon_shop_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRequired. Public Amazon Shop storefront URL.
cursorNoPagination cursor returned by a previous response.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without the description. The description adds two behavioral facts not in the annotations: results are cursor-paginated, and absent optional fields should be omitted rather than nulled. However, 'Send only url' actively misdescribes the call contract for a tool whose schema requires context and llm_model, which undercuts the value of what it does add.

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?

Three short sentences, front-loaded with the resource and then the required argument, with no filler or restated title. The size is well matched to a simple single-resource fetch, though the last two sentences spend words on a call-shape instruction that is both partly redundant with the schema and partly wrong.

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

Completeness3/5

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

There is no output schema, so the description should carry some burden of describing what comes back; it only implies a paginated result set via the cursor mention, without saying what a storefront record contains. More seriously, the parameter guidance omits the two required fields (context, llm_model) and the conversation_id handshake that the schema insists on, leaving an agent to reconcile contradictory instructions on its own.

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

Parameters2/5

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

Schema description coverage is 100%, so a baseline of 3 would apply if the description were merely redundant. Instead the description adds a claim that conflicts with the schema: it says to send only url plus cursor, while the schema marks context and llm_model as required and documents conversation_id. An agent following the description literally would emit an invalid call, so this is worse than adding nothing.

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 states a specific verb and resource: 'Get a creator Amazon Shop storefront by URL,' which is concrete enough that an agent knows exactly what entity is fetched. It does not name or contrast with any sibling (e.g. shopify_page_get, ko_fi_shop_item_get), so the platform distinction must be inferred from the tool name rather than the description.

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

Usage Guidelines2/5

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

The only procedural guidance is about call shape ('Send only url, plus cursor from a previous response'), not about when to choose this tool versus a sibling or what preconditions must hold. It gives no signal about what kind of URL qualifies, what happens on a non-storefront URL, or when to follow a cursor versus start fresh.

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