Skip to main content
Glama
Sign In
Mintline MCP Server

Mintline MCP Server

by mintlineai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_export

Retrieve export job status and obtain a signed download URL that expires in 1 hour.

Instructions

Get export. Retrieve export job status and download URL. The download URL is a signed S3 URL that expires in 1 hour.

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": {
      "id": "<id>"
    },
    "name": "get_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesExport job ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.9

TDQS

B3.4/5.0
Behavior3/5

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

Discloses that the download URL is a signed S3 URL expiring in 1 hour, but does not detail status states, error handling, or retry behavior. With no annotations, the description provides partial transparency.

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 sentences with no wasted words. The first sentence is terse; the second adds essential expiry information. Could be structured more clearly (e.g., bullet points) but is efficient.

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?

Given no output schema or annotations, the description covers core purpose and a key behavioral detail (URL expiry) but omits status values, error scenarios, and how to use the URL.

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% (one parameter 'id' described as 'Export job ID'). The description does not add extra meaning beyond the schema, achieving baseline 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?

Description clearly states the verb 'Get' and resource 'export', and specifies it retrieves 'export job status and download URL', distinguishing it from related tools like 'create_export' and 'list_exports'.

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 (e.g., after creating an export, waiting for completion) or alternatives. The description implies a prerequisite (export job ID) but does not explain context.

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