Skip to main content
Glama
Minimax MCP Server

Minimax MCP Server

by chehcore

List Changed Minimax Records

minimax_list_sync_candidates
Read-onlyIdempotent

Lists record IDs created, changed, or deleted within a time window for a specified resource, so you can answer "what changed since..." without paging all records.

Instructions

List IDs of records created, changed or deleted in a time window -- the efficient way to answer "what changed since ..." without paging everything.

Returns: str: JSON {Rows: [{ID, RowVersion, RecordDtModified, ...}], TotalRows, ...}.

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": {
      "params": "<params>"
    },
    "name": "minimax_list_sync_candidates"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, and non-destructive behavior. The description adds useful context beyond that: it covers created/changed/deleted records, time-window filtering, and incremental sync efficiency, though it does not discuss auth, rate limits, or pagination of results.

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 description is short and front-loads the core purpose. The return-shape block is somewhat redundant because an output schema exists, but it is still brief and does not obscure the main point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the annotations and output schema, the description gives enough behavioral context for an agent to understand the tool's role in incremental sync. It is not fully complete on parameter semantics and alternatives, but the major behavioral gaps are covered by structured metadata.

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?

The description only vaguely implies time-window parameters and does not explain the required resource enum, parent_id for nested resources, sync_mode, or organisation_id. With the reported low schema description coverage, the description should compensate for those gaps but does not.

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: listing IDs of records created, changed, or deleted in a time window. It also contrasts this with paging everything, which helps distinguish the tool's purpose, though it does not explicitly name sibling tools like search_records.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear use case: answering 'what changed since ...' efficiently without paging everything. It does not provide explicit exclusions or name alternative sibling tools, but the intended context is clear.

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