Skip to main content
Glama
Polymarket MCP Server

Polymarket MCP Server

by yashhsm

list_markets

Fetch Polymarket markets with filtering by tags, pagination, sorting, and closed status to find relevant prediction markets.

Instructions

List Polymarket markets with optional filtering by tags, pagination, and sorting

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results to return (max 100)
orderNoField to order by
closedNoInclude closed markets
offsetNoPagination offset
tag_idNoFilter by tag ID
ascendingNoSort in ascending order
related_tagsNoInclude related tags
exclude_tag_idNoExclude specific tag IDs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only gives a high-level summary and omits important behavior such as whether closed markets are excluded by default, the max-limit behavior beyond the schema, and what the response/pagination semantics are.

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?

The description is a single front-loaded sentence with no filler. It efficiently communicates the core operation and the broad optional capabilities.

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?

The input schema is rich and documents all parameters, which reduces what the description must cover. Still, with no output schema or annotations, the description does not clarify default market visibility, sorting behavior, or return shape, leaving meaningful gaps for an 8-parameter listing tool.

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 coverage is 100%, so all eight parameters are already documented in the input schema. The description mentions tag filtering, pagination, and sorting at a category level but adds no parameter-specific meaning, defaults, or syntax 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 states a specific verb and resource: list Polymarket markets, with optional tag filtering, pagination, and sorting. It is clearly distinct from singular retrieval tools like get_market_by_slug and from list_events/list_tags by resource, though it does not explicitly name alternatives.

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?

It implies usage for browsing or filtering markets via the mention of optional filtering, pagination, and sorting. However, it does not state when to use this versus search_polymarket, get_market_by_slug, or other listing tools, and gives no exclusions.

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