Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get several Polymarket markets

polymarket_markets_batch_get
Read-onlyIdempotent

Retrieve up to 100 Polymarket markets using condition IDs or outcome token IDs, with optional locale translation for titles and market questions.

Instructions

Get up to 100 Polymarket markets by condition id or token id. Optional inputs: conditionIds, tokenIds and locale.

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": "polymarket_markets_batch_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoTranslate titles and market questions into this language. Descriptions stay in English.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
tokenIdsNoOutcome token ids to look up. Repeat the parameter or separate ids with commas.
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.
conditionIdsNoCondition ids to look up. Repeat the parameter or separate ids with commas.
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.4/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 without the description. The description adds only the 100-item ceiling; it says nothing about ordering of results, behavior with unknown ids, or the fact that two parameters (context, llm_model) are mandatory on every call.

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, front-loaded with the verb, resource and limit, with no wasted wording. The second sentence is a bare parameter enumeration that largely duplicates the schema, which keeps it just short of a 5.

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?

For a batch lookup with no output schema, the description covers what goes in but not what comes back (market fields, ordering, partial-miss behavior). The sequencing constraint around conversation_id and the mandatory analytics parameters live only in the schema, leaving the description adequate but not self-sufficient.

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 the schema already explains conditionIds, tokenIds, locale, context, llm_model and conversation_id in more detail than the description. The description's list of 'optional inputs' adds nothing beyond the schema and omits the required parameters entirely, so baseline 3 applies.

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 ('Get ... Polymarket markets'), the batch cardinality ('up to 100'), and the two accepted lookup keys (condition id or token id). An agent can distinguish it from the single-market sibling by the explicit batch framing, though the description never names the alternatives.

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?

The 'up to 100 ... by condition id or token id' phrasing implies the batch use case and the key types, but there is no explicit when-to-use versus polymarket_market_get (single lookup) or polymarket_markets_list. Guidance is inferred rather than stated.

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