Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Stan Store creators

stan_store_creators_list
Read-onlyIdempotent

Lists Stan Store creators page by page, filtered by handle prefix or product availability. Use it to browse or search creators and paginate with a cursor.

Instructions

List Stan Store creators with a cursor, filtered by handle prefix or by whether they have products. Optional inputs: cursor, limit, prefix and hasProducts. Returns a list (use cursor when paginated).

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

Input Schema

NameRequiredDescriptionDefault
limitNoCreators per page, 1 to 1000. Default: 100.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same `prefix` and `hasProducts` filters.
prefixNoOnly creators whose handle starts with this prefix (case-insensitive); 1 to 47 letters, digits, dots, underscores or hyphens, e.g. `Al`. A filtered page can be empty while `page.hasMore` is true; follow `nextCursor`.
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.
hasProductsNoFilter on whether the creator has at least one product page. An unknown count at a page boundary never matches `false`.
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 the safety profile is covered. The description adds only a cursor/pagination pointer ('use cursor when paginated'), while richer behavioral details (cursor bound to same filters, empty page while hasMore is true) live in the schema rather than the description.

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 front-loaded sentences with a clear purpose clause. The middle clause enumerating optional inputs is somewhat redundant with the schema, a minor waste, but nothing is verbose or buried.

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 list tool with a fully documented 7-param schema and no output schema, the description covers purpose, filters and pagination. The only shortfall is that it does not sketch the shape of returned items, though annotations and schema carry most of the remaining burden.

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%, so the schema already documents every parameter with formats and constraints. The description merely re-lists the optional parameters by name without adding meaning, so baseline 3 is appropriate.

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?

States a specific verb and resource ('List Stan Store creators') plus its scoping mechanisms (cursor, handle prefix, hasProducts filter). An agent can distinguish this from the singular 'stan_store_creator_get' by name alone, but the description never explicitly contrasts with siblings.

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: enumerate creators, optionally narrowing by prefix or product presence. There is no explicit when-to-use-vs-alternative guidance (e.g., when to use this instead of stan_store_creator_get for a single lookup) and no stated exclusions, so guidance stays at the inferred level.

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