Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Polymarket user activity

polymarket_user_activity_list
Read-onlyIdempotent

Fetch a Polymarket wallet's trades, splits, merges, redemptions, and other activity with filters and cursor pagination for auditing or tracking.

Instructions

List a Polymarket wallet's trades, splits, merges and redemptions. Requires wallet. 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": {
      "wallet": "<wallet>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "polymarket_user_activity_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOnly activity at or before this time, unix seconds.
fromNoOnly activity at or after this time, unix seconds.
typeNoOnly this kind of activity.
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.
walletYesRequired. Wallet address: 0x followed by 40 hex digits.
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.
conditionIdNoOnly activity in this market.
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, openWorldHint, and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds the wallet requirement and the fact that results are a list with cursor pagination, but says nothing about default page size, ordering, empty-result behavior, or the server-side conversation_id sequencing handshake that the schema hints at.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the capability stated first and the operational note second; nothing is padded or redundant. Every clause earns its place.

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 ten parameters, three required, and no output schema, the description covers the essential call shape but not the return structure beyond "a list". The mismatch between the four activity types named and the eight allowed by the enum leaves an agent with an incomplete picture of what can be filtered.

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 every parameter is already documented in the schema, making 3 the baseline. The description's cursor remark merely restates the schema's own note about passing page.nextCursor, and it adds no meaning for the from/to, type, conditionId, or limit filters.

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 a Polymarket wallet's trades, splits, merges and redemptions") and scopes it to a single wallet, which implicitly separates it from market-wide siblings like polymarket_market_trades_list. It stops short of explicitly distinguishing itself from polymarket_user_positions_list or polymarket_user_pnl_list, and it names only four of the eight activity types the schema's enum allows (REWARD, CONVERSION, YIELD, MAKER_REBATE are omitted).

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?

"Requires `wallet`" gives a hard prerequisite and "use cursor when paginated" gives a follow-up rule, but there is no guidance on when to choose this over user positions, PnL, or market-level trades. Usage is implied by the tool name 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