AIsa Finance

List markets

get_polymarket_markets

Read-onlyIdempotent

List markets with offset based pagination and filters.

Published reference price: $0.00044 USD per successful request. Account-specific pricing and final settlement may differ.

Input Schema

Name	Required	Description
`id`	No
`cyom`	No
`slug`	No
`limit`	No
`order`	No	Comma-separated list of fields to order by
`closed`	No
`offset`	No
`tag_id`	No
`game_id`	No
`ascending`	No
`include_tag`	No
`end_date_max`	No
`end_date_min`	No
`question_ids`	No
`related_tags`	No
`condition_ids`	No
`clob_token_ids`	No
`start_date_max`	No
`start_date_min`	No
`volume_num_max`	No
`volume_num_min`	No
`rewards_min_size`	No
`liquidity_num_max`	No
`liquidity_num_min`	No
`sports_market_types`	No
`uma_resolution_status`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 19, 2026

addedInput schema / properties / closed / oneOf

Added value: +[
+  {
+    "type": "boolean"
+  },
+  {
+    "enum": [
+      "any"
+    ],
+    "type": "string"
+  }
+]

removedInput schema / properties / closed / type
```
Removed value: -"boolean"
```

Changed42 schema fields changedOct 15, 2026
- removedInput schema / properties / ascending / description
```
Removed value: -"Sort ascending when true."
```
- removedInput schema / properties / ascending / example
```
Removed value: -false
```
- removedInput schema / properties / clob_token_ids / description
```
Removed value: -"Filter by one or more CLOB token IDs."
```
- removedInput schema / properties / closed / description
```
Removed value: -"Filter by whether the market is closed."
```
- removedInput schema / properties / closed / example
```
Removed value: -false
```
- removedInput schema / properties / condition_ids / description
```
Removed value: -"Filter by one or more market condition IDs."
```
- removedInput schema / properties / condition_ids / example
```
Removed value: -[
-  "0x1fad72fae204143ff1c3035e99e7c0f65ea8d5cd9bd1070987bd1a3316f772be"
-]
```
- addedInput schema / properties / cyom
```
Added value: +{
+  "type": "boolean"
+}
```
- removedInput schema / properties / end_date_max / description
```
Removed value: -"Filter markets ending before this ISO timestamp."
```
- removedInput schema / properties / end_date_max / example
```
Removed value: -"2026-01-01T00:00:00Z"
```
- removedInput schema / properties / end_date_min / description
```
Removed value: -"Filter markets ending after this ISO timestamp."
```
- removedInput schema / properties / end_date_min / example
```
Removed value: -"2025-01-01T00:00:00Z"
```
- addedInput schema / properties / game_id
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / id / description
```
Removed value: -"Filter by one or more Polymarket market IDs."
```
- removedInput schema / properties / id / example
```
Removed value: -[
-  540817
-]
```
- removedInput schema / properties / include_tag / description
```
Removed value: -"Include tag metadata when true."
```
- removedInput schema / properties / include_tag / example
```
Removed value: -true
```
- removedInput schema / properties / limit / description
```
Removed value: -"Maximum number of markets to return."
```
- removedInput schema / properties / limit / example
```
Removed value: -20
```
- addedInput schema / properties / liquidity_num_max
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / liquidity_num_min
```
Added value: +{
+  "type": "number"
+}
```
- removedInput schema / properties / offset / description
```
Removed value: -"Number of markets to skip for offset-based pagination."
```
- removedInput schema / properties / offset / example
```
Removed value: -0
```
- changedInput schema / properties / order / description
```
Previous value: -"Comma-separated list of fields to order by."New value: +"Comma-separated list of fields to order by"
```
- removedInput schema / properties / order / example
```
Removed value: -"volume"
```
- addedInput schema / properties / question_ids
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- addedInput schema / properties / related_tags
```
Added value: +{
+  "type": "boolean"
+}
```
- addedInput schema / properties / rewards_min_size
```
Added value: +{
+  "type": "number"
+}
```
- removedInput schema / properties / slug / description
```
Removed value: -"Filter by one or more market slugs."
```
- removedInput schema / properties / slug / example
```
Removed value: -[
-  "new-rhianna-album-before-gta-vi-926"
-]
```
- addedInput schema / properties / sports_market_types
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- removedInput schema / properties / start_date_max / description
```
Removed value: -"Filter markets starting before this ISO timestamp."
```
- removedInput schema / properties / start_date_max / example
```
Removed value: -"2026-01-01T00:00:00Z"
```
- removedInput schema / properties / start_date_min / description
```
Removed value: -"Filter markets starting after this ISO timestamp."
```
- removedInput schema / properties / start_date_min / example
```
Removed value: -"2025-01-01T00:00:00Z"
```
- removedInput schema / properties / tag_id / description
```
Removed value: -"Filter by tag ID."
```
- removedInput schema / properties / tag_id / example
```
Removed value: -1
```
- addedInput schema / properties / uma_resolution_status
```
Added value: +{
+  "type": "string"
+}
```
- removedInput schema / properties / volume_num_max / description
```
Removed value: -"Maximum total volume."
```
- removedInput schema / properties / volume_num_max / example
```
Removed value: -1000000
```
- removedInput schema / properties / volume_num_min / description
```
Removed value: -"Minimum total volume."
```
- removedInput schema / properties / volume_num_min / example
```
Removed value: -1000
```
First observedSep 15, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds that pagination is offset-based, which is mildly useful, but says nothing about rate limits, default/max page size, or the fact that results reach live external data. The injected pricing block is commerce boilerplate, not behavioral disclosure.

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?

The substantive sentence is short and front-loaded with the verb and resource. The trailing pricing block is injected boilerplate rather than author text, so it is noise in the payload but not a structure failure of the description itself.

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?

An output schema exists, so return values need not be explained. However, for a tool with 26 optional parameters and almost no schema documentation, the description is far too thin: no filter semantics, no pagination defaults, no guidance on combining filters, and no routing to sibling market/event tools.

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

Parameters2/5

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

With 26 parameters at 4% schema coverage, the schema is nearly silent (only 'order' is documented), so the description must carry the burden and does not. It generically says 'filters' without naming or explaining any of the filters (closed, tag_id, volume_num_min, uma_resolution_status, etc.), leaving most parameters semantically opaque.

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 (List) and resource (markets) with the platform implied by the tool name, and mentions pagination plus filters. It is clear on its own, but it never distinguishes itself from the sibling get_kalshi_markets or clarifies what a 'market' is versus an 'event' from get_polymarket_events, so an agent must infer the boundary.

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 explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as get_kalshi_markets or get_polymarket_events. The only usage hint is 'offset based pagination and filters', which describes capability rather than context for selecting this tool.

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

All AIsa Finance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?