Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Polymarket trades

polymarket_trades_list
Read-onlyIdempotent

List Polymarket trades across all markets or one wallet, with filters for event, side, minimum size, and time range; paginate results with a cursor.

Instructions

List Polymarket trades across all markets or one wallet. Optional inputs: wallet, eventId, side, minSize, from and 3 more. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "polymarket_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.
walletNoOnly this wallet's trades. Without it the list is the live tape across all markets.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
eventIdNoOnly trades in this event.
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.
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.4/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 the safety profile is covered. The description adds only that results are a list and that a cursor is used when paginated, with no mention of rate limits, result caps, or ordering. That is a modest but real increment over the annotations.

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 scope stated first, filters second, and return/pagination last — front-loaded and free of padding. The vague 'and 3 more' is the one weak spot, since it forces a schema lookup anyway and adds little.

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?

With 11 parameters, no output schema, and rich annotation coverage, the description covers scope, filter category and pagination, which is most of what an agent needs. It omits the two required bookkeeping parameters (context, llm_model) and gives no sense of ordering or result size, leaving gaps for a tool of this complexity.

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 each parameter is documented in detail, including the wallet's live-tape semantics and the cursor's page.nextCursor contract. The description only enumerates a partial list of optional inputs ('wallet, eventId, side, minSize, from and 3 more') without adding format or interaction meaning, 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?

States a specific verb and resource ('List Polymarket trades') plus the two scopes it covers: all markets (the live tape) or a single wallet. It does not name any sibling, so an agent must infer on its own why this differs from polymarket_market_trades_list or polymarket_event_trades_list without opening their schemas.

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?

The phrase 'across all markets or one wallet' implies when to use it, and the cursor note implies iterative pagination, but there is no explicit when-to-use versus the market-scoped or perps trade siblings, and no stated exclusions or prerequisites. Guidance is implied rather than stated.

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