Skip to main content
Glama
Polymarket MCP Server

Polymarket MCP Server

by yashhsm

search_polymarket

Search Polymarket markets, events, and profiles through the public API to locate prediction topics and filter results by tags, status, and sort order.

Instructions

Search Polymarket markets, events, and profiles using the public search API

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": {
      "q": "<q>"
    },
    "name": "search_polymarket"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query (required)
pageNoPage number
sortNoSort field
cacheNoUse cached results
ascendingNoSort ascending
optimizedNoUse optimized search
events_tagNoFilter by event tags
recurrenceNoFilter by recurrence
search_tagsNoInclude tags in search
events_statusNoFilter by event status
exclude_tag_idNoExclude specific tag IDs
limit_per_typeNoLimit results per type
search_profilesNoInclude profiles in search
keep_closed_marketsNoInclude closed markets (0 or 1)

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 burden. It does disclose that the API is public, which usefully signals no authentication is required, but it says nothing about pagination behavior, result-size limits, rate limits, or what the combined filters actually do — significant gaps for a 14-parameter tool with no stated side effects or return shape.

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 no wasted words, and the core purpose comes first. It is efficient, though for a tool of this complexity the brevity borders on under-specification rather than tight writing.

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?

With 14 parameters, no annotations, and no output schema, the description should do substantial work, but it provides one line covering only the high-level purpose. An agent gets no guidance on default behavior, result ordering, pagination semantics, or how search_profiles/keep_closed_markets alter the result set.

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 is already documented in the input schema, establishing the baseline of 3. The description adds no meaning beyond the schema — it never explains how filters like events_status, recurrence, or keep_closed_markets interact, nor what 'optimized' changes.

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 (search) and concrete resources (markets, events, profiles), which lets an agent distinguish keyword search from the slug-based lookups among its siblings (get_market_by_slug, get_event_by_slug). It does not explicitly contrast with list_markets/list_events, so the differentiation is implied rather than stated.

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 statement about when not to use it, and no named alternative. The word 'search' hints at keyword lookup versus browsing, but an agent must infer that on its own; nothing tells it when to reach for search_polymarket rather than list_markets.

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