Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Polymarket event annotations

polymarket_event_annotations_list
Read-onlyIdempotent

Retrieve dated explanations for a Polymarket event's price movements by event ID or slug. Use it to understand why an event's odds shifted over time.

Instructions

List the dated explanations of a Polymarket event's price moves. Requires eventIdOrSlug. Returns a list.

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

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
outcomeNoOnly annotations about this outcome, matched on its name without regard to case.
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.
eventIdOrSlugYesRequired. Event id (digits) or slug, as in polymarket.com/event/{slug}.
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.2/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 safety and repeatability are covered. The description adds the semantic content of what is returned ('dated explanations of price moves') and that the result is a list, but says nothing about ordering, volume, or whether events without annotations return an empty list.

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 with the substantive definition front-loaded and no filler. 'Returns a list' is slightly thin but earns its place since no output schema exists to convey the return type.

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 read-only listing tool with no output schema, the description should at least hint at the annotation record shape and whether results are ordered or paginated, and it only says 'Returns a list'. Enough to select the tool correctly, not enough to predict the response.

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 all five parameters, including the outcome filter and the context/llm_model/conversation_id plumbing, are documented in the schema itself. The description's only parameter mention repeats 'Requires eventIdOrSlug', which the schema already states as required with its id/slug format, adding no new meaning.

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 gives a specific verb and resource and even disambiguates the vague term 'annotations' into 'dated explanations of a Polymarket event's price moves', so an agent knows it is returning narrative context tied to price movement rather than raw comments or insights. It does not explicitly distinguish itself from near siblings such as polymarket_event_comments_list or polymarket_event_insights_get, which keeps it at a 4.

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?

There is no statement of when to pick this tool over the event comments, insights, or price-history siblings. 'Requires eventIdOrSlug' is a prerequisite, not usage guidance, and no exclusion or alternative is named.

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