Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Polymarket market holders

polymarket_market_holders_list
Read-onlyIdempotent

List the largest holders of each outcome in a Polymarket market using its condition ID, with pagination support for retrieving additional results.

Instructions

List the largest holders of each outcome of a Polymarket market. Requires conditionId. 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": {
      "conditionId": "<conditionId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "polymarket_market_holders_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page, 1–1000. Default: 20.
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.
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.
includePnlNoAdd each holder's entry price, cost, current value and profit. Default: false.
minBalanceNoOnly holders with at least this many shares.
conditionIdYesRequired. Condition id of the market: 0x followed by 64 hex digits.
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 without the description. The description adds that results are per-outcome, that output is a list, and that cursor pagination applies — useful but thin for a tool with 8 params including analytics-only ones (llm_model, context) whose behavior is left entirely to the schema.

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 core action front-loaded and the prerequisite second, so an agent can act after the first line. The trailing 'use cursor when paginated' is slightly awkward phrasing but carries real information, and there is no padding.

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 read-only listing tool whose annotations cover the safety profile and whose schema is fully described, the description supplies the essentials: what is listed, the required key, and how to paginate. Return field details are not needed since the output is a simple list, though a note on whether holders are split per outcome token in the response would close the last gap.

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 parameters are already fully documented and the baseline is 3. The description only restates the `conditionId` requirement and cursor usage, both of which are already spelled out in the schema, and says nothing about the effect of includePnl or minBalance beyond what the schema states.

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 the largest holders of each outcome of a Polymarket market' — and the per-outcome scoping is a meaningful qualifier that distinguishes it from a plain position or leaderboard listing. It does not name any sibling tool or explain how it differs from polymarket_user_positions_list or polymarket_leaderboard_list, so it stops short of a 5.

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?

Names a hard prerequisite ('Requires `conditionId`') and a pagination procedure ('use cursor when paginated'), which is genuine usage guidance. However, there is no statement of when to prefer this over the related holder/position tools in the sibling set, nor any exclusion of cases where it is the wrong choice.

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