Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polymarket_activity_trades

Retrieve Polymarket public trade activity with filters for market, event, taker-only, and minimum amount. Get normalized trade rows from the Data API for analysis or display.

Instructions

List Polymarket activity trades. Returns normalized public trade rows used by Polymarket's /activity page from credential-free Data API trades JSON. The taker_only enum accepts true and false; the filter_type enum accepts CASH; the filter_amount enum accepts 1, 5, 10, 100, 1000, 10000, and 100000.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum trades, defaults to 50 and supports up to 100
marketNoOptional market condition id
offsetNoResult offset, defaults to 0 and supports up to 10000
event_idNoOptional Polymarket event id
taker_onlyNoTaker-only filter
filter_typeNoActivity amount filter type
filter_amountNoMinimum filtered amount

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.17.5
    • addedInput schema / properties / filter_amount / enum
      Added value: +[
+  "1",
+  "5",
+  "10",
+  "100",
+  "1000",
+  "10000",
+  "100000"
+]
    • addedInput schema / properties / filter_type / enum
      Added value: +[
+  "CASH"
+]
    • addedInput schema / properties / taker_only / enum
      Added value: +[
+  "true",
+  "false"
+]
  2. Addedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses that the data is credential-free and public, which is useful, but it doesn't state whether the operation is read-only, how results are ordered, or what fields the normalized rows contain. These are meaningful gaps for a list tool.

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 sentences with the core purpose front-loaded. The enum listing is somewhat redundant with the schema but is compact and easy to scan. No filler or irrelevant detail.

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 no output schema, the description should explain return values more concretely. Saying 'normalized public trade rows' is vague and doesn't cover pagination, ordering, or row field names. The tool is simple enough that the description is adequate, but noticeable gaps remain.

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 baseline is 3. The description repeats enum values already present in the schema (`taker_only`, `filter_type`, `filter_amount`) without adding deeper meaning about how filters interact or affect results. It adds no significant semantic value 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 uses a specific verb and resource: 'List Polymarket activity trades.' It further clarifies by tying the data to Polymarket's `/activity` page and the credential-free Data API, which helps distinguish it from other Polymarket siblings like orderbook or market detail tools. It doesn't explicitly name sibling alternatives, but the resource is specific enough.

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 description implies when to use the tool by describing the exact data source and context (`/activity` page, normalized public trade rows). However, it does not explicitly state when not to use it or mention alternative tools, leaving the routing decision mostly to inference.

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