Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Polymarket perps trades

polymarket_perps_trades_list
Read-onlyIdempotent

Retrieve recent Polymarket perps trades for a specific instrument ID, using time-range filters and cursor pagination to page through results.

Instructions

List recent Polymarket perps trades. Requires instrumentId. 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": {
      "instrumentId": "<instrumentId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "polymarket_perps_trades_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd of the range, unix seconds. Default: now.
fromNoStart of the range, unix seconds. Default: 24 hours before `to`.
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.
instrumentIdYesRequired. Perps instrument id from the instruments list.
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, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds only that results are cursor-paginated and recent-scoped, and says nothing about ordering, page size, or rate limits beyond that.

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 the purpose and then the key requirement; no filler. It is arguably too terse rather than wasteful.

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 7-parameter tool with no output schema, the description is minimally adequate: it covers pagination and the required id but does not explain the shape of a returned trade record or the trade-off with the non-perps trade listers.

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%, including detailed text for from/to defaults, cursor, context, llm_model and conversation_id, so the baseline of 3 applies. The description only echoes the instrumentId requirement and the cursor convention, adding no meaning beyond the schema.

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 gives a specific verb and scoped resource ('List recent Polymarket perps trades') and names the required key ('Requires instrumentId'), which distinguishes it from spot-trade siblings by domain. It stops short of explicitly contrasting itself with polymarket_trades_list or polymarket_market_trades_list.

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?

Usage is only implied: 'Requires instrumentId' and 'use cursor when paginated' tell the agent prerequisites but not when to pick this over the spot/market trade listers or when not to use it.

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