DeepScout

Get an export file

scout_get_export

Read-only

Get a temporary URL of an export file of a project. Give the dataset of the file from scout_list_exports, and its website_id if the file has one. The file exists after the job is COMPLETED.

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": {
      "dataset": "<dataset>",
      "project_id": "<project_id>"
    },
    "name": "scout_get_export"
  }
}

Input Schema

Name	Required	Description	Default
`dataset`	Yes
`project_id`	Yes
`website_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The annotations already indicate a safe read-only operation, and the description adds useful behavioral context: the returned URL is temporary and the export file is available only after job completion. It does not discuss error behavior or URL lifetime, but this is reasonable given the annotation coverage and output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three short sentences with no wasted text. The primary purpose is front-loaded, followed by parameter sourcing and the completion precondition.

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?

The description covers the key workflow and availability precondition, and an output schema exists to explain the return value. Minor gaps remain around project_id semantics and what happens when the job is not completed, but the definition is sufficient for correct invocation.

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 0%, so the description must carry parameter meaning. It explains where dataset comes from and when website_id applies, but project_id is not described, leaving one of three parameters undocumented beyond its name and type.

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 states a specific verb and resource: it returns a temporary URL for an export file of a project. This clearly distinguishes it from scout_list_exports, which is referenced as the source for identifying the export dataset.

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 clear operational guidance: the dataset comes from scout_list_exports, website_id is supplied only if the file has one, and the file exists only after the job is COMPLETED. It does not explicitly state when not to use this tool or name an alternative beyond the prerequisite listing tool.

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

All DeepScout 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.