Skip to main content
Glama
Polymarket MCP Server

Polymarket MCP Server

by yashhsm

get_user_activity

Retrieve a Polymarket user's activity by wallet address, including trades, splits, merges, and rewards, with filters for activity type, market, event, and pagination.

Instructions

Get user activity from Polymarket including trades, splits, merges, and rewards

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": {
      "user": "<user>"
    },
    "name": "get_user_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesUser wallet address (required)
limitNoMax number of activities (default: 100, max: 500)
typesNoFilter by activity types (e.g., TRADE, SPLIT, MERGE, REWARD)
marketNoFilter by condition IDs
offsetNoPagination offset (default: 0, max: 10000)
eventIdNoFilter by event IDs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not meet it. It never states that this is a read-only operation, says nothing about result ordering, pagination behavior, whether the wallet must be a Polymarket participant, or what the response items look like.

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?

A single front-loaded sentence with the resource and the returned scope stated immediately. It is efficient, though the enumeration of activity types consumes space that could have been spent on usage guidance.

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

Completeness2/5

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

For a six-parameter query tool with no annotations and no output schema, the description is thin. The agent gets no sense of return shape, ordering, or how pagination interacts with the filters, all of which must be guessed.

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 including user, limit, offset, types, market and eventId is already documented in the schema. The description adds no parameter-level meaning beyond restating the activity kinds that the types field already lists as examples.

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 ('Get user activity from Polymarket') and enumerates the activity kinds returned (trades, splits, merges, rewards), so the scope is clear. It does not explicitly differentiate itself from the sibling get_trades_by_wallet, even though it plainly returns a superset of that tool's data.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no named alternative. The enumeration of activity types weakly implies this tool is broader than get_trades_by_wallet, but the agent must infer that rather than being told.

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