polymarket-mcp-server

Overview Schema Source Related Servers Discussions Admin

Get Polymarket wallet activity

polymarket_get_user_activity

Read-onlyIdempotent

Retrieve a wallet's full on-chain activity feed, including trades, splits, merges, redeems, rewards, deposits, and withdrawals, to track complete history beyond open positions.

Instructions

Get a wallet's full on-chain ACTIVITY feed — beyond open positions: trades plus splits, merges, redeems, rewards, deposits and withdrawals.

Complements polymarket_get_positions (current holdings) and polymarket_get_trades (just trades) with the complete history.

Args:

wallet (string): 0x… address (42 chars).
type (string[], optional): filter to types like TRADE, SPLIT, MERGE, REDEEM, REWARD, DEPOSIT, WITHDRAWAL (default: all).
limit (number): max entries to request, 1-500 (default 50). At most 200 are returned.
response_format ('markdown' | 'json'): default 'markdown'.

Returns: { wallet, count, truncated, activities:[{ type, timestamp, iso, side, outcome, size, usdcSize, price, conditionId, title, slug, transactionHash }] }. The 'truncated' flag is true when more entries existed than were returned. An unknown wallet returns 0 activities.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`type`	No	Filter to these activity types (default: all).
`limit`	No	Max activity entries to request (1-500, default 50). At most 200 are returned; past that the response is capped and flagged with `truncated`.
`wallet`	Yes	Public wallet address (0x…, 42 chars).
`response_format`	No	Output format: 'markdown' (concise, human-readable; default) or 'json' (full structured data).	markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`wallet`	Yes
`truncated`	Yes
`activities`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 28, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description still adds genuinely useful behavior beyond that: the 200-entry return cap with a 'truncated' flag, and that an unknown wallet returns 0 activities rather than erroring.

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?

Front-loads the core scope and sibling differentiation, then uses clean Args/Returns sections. Every line carries information and nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read tool with full annotations and an output schema, the description covers scope, filtering, pagination/cap behavior, and error-case behavior (unknown wallet). Nothing an agent needs in order to call it correctly is missing, though the inline Returns block is mildly redundant given the output schema.

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 schema already documents all four parameters, and baseline 3 applies. The description largely repeats the schema, and its type list (TRADE, SPLIT, MERGE, REDEEM, REWARD, DEPOSIT, WITHDRAWAL) is actually a subset of the schema enum, which also includes CONVERSION, MAKER_REBATE, TAKER_REBATE, REFERRAL_REWARD, and YIELD.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Get a wallet's full on-chain ACTIVITY feed') and explicitly scopes it beyond the two closest siblings, naming them: 'Complements polymarket_get_positions (current holdings) and polymarket_get_trades (just trades) with the complete history.' An agent can tell exactly what this returns versus the alternatives without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear context and names the alternatives: use get_positions for current holdings and get_trades for trades only, and this tool when the complete history is needed. It stops short of explicit when-not guidance or prerequisites, so it falls just below the top bar.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.