Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Polymarket market trades

polymarket_market_trades_list
Read-onlyIdempotent

List the public trade tape for a Polymarket market, newest first, using its conditionId; filter by time, side, and minimum size, then page through results with a cursor.

Instructions

List the public trade tape of one Polymarket market, newest first. 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_trades_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOnly trades at or before this time, unix seconds.
fromNoOnly trades at or after this time, unix seconds.
sideNoOnly trades on this side.
limitNoItems per page, 1–1000. Default: 100.
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.
minSizeNoOnly trades of at least this many US dollars.
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.
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.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds genuinely new behavior: results are a public tape, ordered newest first, and pagination is handled via cursor — details the annotations do not convey.

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 purpose and scope, no wasted wording. The final clause 'Returns a list (use cursor when paginated)' is slightly redundant with the schema but still useful as a quick summary.

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 10-parameter list endpoint with no output schema, the description omits what a trade record contains and how results are shaped beyond 'a list'. It covers the essentials needed to call the tool, but an agent gets no sense of return payload richness.

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% and every filter (from/to, side, minSize, limit, cursor, conditionId) is already documented in the schema. The description only restates the `conditionId` requirement and cursor usage, adding no syntax or filter semantics beyond structured data.

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 public trade tape of one Polymarket market' — plus scope and ordering ('newest first'). The phrase 'one Polymarket market' implicitly separates it from the cross-market polymarket_trades_list, though no sibling is named explicitly.

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 says the tool is scoped to a single market and that `conditionId` is required, which implies when to pick it over a broader trade list. However, it never states when-not to use it or points to the perps/global trade alternatives, leaving routing to inference from the name.

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