Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Polymarket

polymarket_search
Read-onlyIdempotent

Search Polymarket events, tags, and profiles by keyword to locate prediction markets, related tags, or user profiles; paginate results as needed.

Instructions

Search Polymarket events, tags and profiles by keyword. Requires query. Returns a list (use page when paginated).

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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "polymarket_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 1–100. Default: 1. Polymarket can stop a deep page early and report `hasMore: false`.
queryYesRequired. Search text. The index is English: other scripts return nothing.
typesNoWhat to search, comma separated: `events`, `tags`, `profiles`. Default: `events,tags`.
localeNoTranslate titles and market questions into this language. Descriptions stay in English.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
limitPerTypeNoItems per page, 1–50. Default: 10.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered without the description's help. The description adds only the return shape ('Returns a list') and a pagination hint, both of which are thin and partly duplicated by the schema's page description. No annotation contradiction.

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 short, front-loaded sentences with no filler; the scope statement comes first and the pagination note second. Minor waste in restating 'Requires `query`', which the schema already marks as required, and the parenthetical is slightly clipped.

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 8 parameters, three of them required (query, context, llm_model) and a non-obvious conversation_id sequencing contract, the description is thin. Saying only 'Requires `query`' understates the required set and gives no hint about the conversation_id handshake, though the fully-populated schema prevents this from being a blocking gap.

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%, including the English-only index caveat, locale enum, page limits and the conversation_id sequencing rule, so the schema carries all parameter meaning. The description adds nothing beyond restating that `query` is required, which is the baseline-3 case when the schema does the heavy lifting.

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?

States a specific verb (search) and enumerates the resource types covered (events, tags, profiles) plus the keyword-based matching mode, so the agent knows exactly what the tool retrieves. It does not differentiate itself from the similarly-scoped sibling polymarket_users_search, so it falls short of a 5.

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?

The only procedural guidance is 'use page when paginated', which is a mechanical hint rather than a when-to-use rule. There is no statement of when to prefer this over polymarket_users_search, polymarket_tags_list, or polymarket_events_list, nor any exclusion or prerequisite beyond the required `query`.

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