Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Stan Store creator

stan_store_creator_get
Read-onlyIdempotent

Fetch a Stan Store creator's profile, social links, payment methods, sections, and all listed products by handle to inspect their store and offerings.

Instructions

Get a Stan Store creator's profile, socials, payment methods, sections and every listed product. Requires handle.

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

Input Schema

NameRequiredDescriptionDefault
handleYesRequired. Stan Store handle, with its canonical case. Letters, numbers, dots, underscores and hyphens; 2 to 47 characters.
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so safety is covered; the description's added value is disclosing that the response is an aggregate containing the creator's full product list. It does not say whether that product list is truncated or paginated, which matters for an aggregate fetch with no output schema.

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?

Two short sentences with the resource and return contents front-loaded, so an agent can stop reading once it knows the scope. The trailing "Requires `handle`" is redundant against the schema's required array and could be dropped.

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?

With no output schema, enumerating the returned fields (profile, socials, payment methods, sections, products) is genuinely useful and largely compensates. Remaining gaps are minor: no note on product pagination or on behavior for an unknown handle, and the description mentions only handle even though three parameters are required.

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%, so handle, context, llm_model, and conversation_id are fully documented in the schema; the description's "Requires `handle`" repeats information already present. Baseline 3 applies since the schema carries the parameter burden.

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 a specific verb and resource ("Get a Stan Store creator's profile") and enumerates the returned facets: socials, payment methods, sections, and every listed product. That scope distinguishes it from sibling listing tools such as stan_store_creators_list or stan_store_product_get, though it never names an alternative outright.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the phrase "every listed product" signals this is the single-call full-profile fetch, useful when an agent needs the creator's entire catalog at once. There is no explicit when-to-use or when-not guidance, and no sibling is named as an alternative.

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