Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Polymarket event comments

polymarket_event_comments_list
Read-onlyIdempotent

Fetch comments and replies for a Polymarket event, sorted newest or oldest, with no depth limit and cursor pagination; requires the event ID.

Instructions

List the comments and replies on a Polymarket event, newest or oldest first, with no depth limit. Requires eventId. 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": {
      "eventId": "<eventId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "polymarket_event_comments_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoOrder of top-level comments by time. Default: `newest`. Polymarket can sort by likes only on a route that stops after 250 rows, so it is not offered here.
limitNoTop-level comments per page, 1–100. Default: 40. Replies come with their parent and do not count towards the limit.
cursorNoPass `page.nextCursor` from the previous response to get the next page. Keep the other filters the same.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
eventIdYesRequired. Event id (digits). Slugs are not accepted here.
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.
holdersOnlyNo`true` keeps comments by people who hold a position.
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, non-destructive and openWorld. The description adds real value by disclosing that replies are returned with parents and that there is no depth limit, plus pagination via cursor. It says nothing about rate limits, whether filtering affects reply inclusion, or auth, so it is useful but not rich.

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, front-loaded with what the tool returns and how ordering works. The final sentence ('Returns a list (use cursor when paginated)') is slightly redundant with the cursor schema description but still earns its place as a quick signal.

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 an eight-parameter read-only list tool with full schema description coverage and no output schema, the description covers the core behavior and pagination model. It omits mention of the holdersOnly filter and the conversation_id requirement, but both are thoroughly documented in the schema, so nothing critical is missing for correct invocation.

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% and the schema descriptions are unusually detailed (sort defaults, limit semantics, cursor echo instructions, holdersOnly, conversation_id protocol). The description only restates required eventId and cursor usage, adding essentially no meaning beyond the schema, 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?

The description names a specific verb and resource (list comments and replies on a Polymarket event) and adds scope details — ordering and 'no depth limit' — that separate it from a shallow comment fetch. It does not explicitly contrast with polymorph sibling tools like polymarket_event_annotations_list, but the resource is unambiguous.

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?

It states the hard prerequisite ('Requires eventId') and gives one conditional usage rule ('use cursor when paginated'). There is no guidance on when to prefer this over related Polymarket event tools or when a filtered variant (e.g. holdersOnly) would be appropriate, leaving usage largely implied.

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