Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

polymarket_activity_trades

List normalized Polymarket activity trades with filters for event, market, amount, and taker-only. Returns public trade rows from Data API.

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
event_idNoOptional Polymarket event id
filter_amountNoMinimum filtered amount
filter_typeNoActivity amount filter type
limitNoMaximum trades, defaults to 50 and supports up to 100
marketNoOptional market condition id
offsetNoResult offset, defaults to 0 and supports up to 10000
taker_onlyNoTaker-only filter
Behavior3/5

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

No annotations provided, so description carries full burden. It states returns 'normalized public trade rows' and is 'credential-free', but does not disclose side effects, rate limits, or behavior with missing parameters. The read-only nature is implied but not explicit.

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 sentences, front-loaded with purpose, then enums. No wasted words. Efficient and clear.

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 7 parameters and no output schema, the description covers basic behavior and enum constraints but lacks examples, typical usage, or explanation of parameter interactions. Adequate but not comprehensive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, but the description adds specific enum values for taker_only, filter_type, and filter_amount, which are not in the schema descriptions. This adds concrete semantics beyond the generic descriptions.

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?

Starts with 'List Polymarket activity trades', a clear verb and resource. Distinguishes from many sibling tools that deal with other aspects like events, markets, tokens, or search. The specific mention of 'activity trades' sets it apart.

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?

No explicit guidance on when to use this tool vs alternatives. While it mentions credential-free and Data API, it doesn't compare to other polymarket tools or specify selection criteria like when to use this vs polymarket_trades or other list tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Crawlora-org/crawlora-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server