Mintline MCP Server

list_exports

Retrieve a paginated list of export jobs from Mintline financial records. Use limit and offset parameters to control the number of items per page and the starting point.

Instructions

List exports. Retrieve a list of export jobs.

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": {
      "limit": "<limit>",
      "offset": "<offset>"
    },
    "name": "list_exports"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	Yes	Items per page
`offset`	Yes	Pagination offset

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.1.9May 6, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided. The description only states 'List exports' without disclosing behavioral traits like pagination behavior, authentication requirements, or whether it returns all exports or only those belonging to the user. For a read operation, the minimal description does not add sufficient transparency beyond the obvious.

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 very short (two sentences) and to the point, with no unnecessary words. However, it could be more efficient by including key details about pagination or export types in the same space.

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?

Given the complexity (20+ sibling tools, no output schema, no annotations), the description is too sparse. It does not explain what export jobs are, what data is returned, or how it differs from related list operations. The tool is left largely underspecified for an AI agent.

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%: both limit and offset have descriptions. The description adds no extra meaning beyond what is in the schema, so it meets the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('List') and the resource ('exports'), and uses the phrase 'Retrieve a list of export jobs' which distinguishes it from related tools like get_export (single export) and create_export.

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?

No guidance on when to use this tool versus alternatives such as list_receipts or list_statements. The description does not mention any context for usage or exclusions.

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