Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Polymarket event insights

polymarket_event_insights_get
Read-onlyIdempotent

Fetches the written market context displayed on a Polymarket event page using its event ID or slug, helping you understand an event's background before analysis.

Instructions

Get the written market context shown on a Polymarket event page. Requires eventIdOrSlug.

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_insights_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
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, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description adds only the hint that the payload is narrative 'written market context' rather than structured fields; it says nothing about response shape, size, or the sequencing constraint the schema references for conversation_id.

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 front-loaded and no filler. The second sentence is largely redundant with the schema's required list and minLength, so it does not fully earn its place.

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?

This is a simple read-only tool with a fully documented schema and no output schema, so the bar is low and the definition is close to sufficient. It still leaves ambiguous what 'insights' actually contains and how it differs from polymarket_event_get, which matters given the large sibling set.

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 four parameters — including the non-obvious analytics-only llm_model and the conversation_id echo rule — are already documented in the schema. The description only repeats that eventIdOrSlug is required, adding no format, slug-vs-id, or lookup semantics beyond it; 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 the written market context shown on a Polymarket event page'), which is more precise than a generic 'get event'. It does not, however, differentiate itself from near-siblings like polymarket_event_get or polymarket_event_annotations_list, so an agent must infer that this returns prose context rather than structured event data.

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 when-to-use guidance at all: no statement of when this is preferable to polymarket_event_get, no exclusions, and no mention of prerequisites such as needing a conversation_id from a prior response. 'Requires `eventIdOrSlug`' is a schema restatement, not usage guidance.

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