Dievio

Export List File

export_list_file

Read-onlyIdempotent

Get a private download link for a COMPLETE list as a CSV, JSON or JSONL file (up to 100,000 contacts). Prefer this when the user wants a file. Dievio streams every page automatically, with no extra credits. Optional columns support nested lead_data fields. Link expires within 15 minutes and is revoked with agent/team access. Give the user the returned link or download it using your file tools.

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": {
      "list_id": "<list_id>",
      "format": "<format>"
    },
    "name": "export_list_file"
  }
}

Input Schema

Name	Required	Description	Default
`format`	Yes		csv
`columns`	No	Optional ordered columns. Supports lead_data.company_website or other nested paths. Omit to preserve all fields; CSV includes the complete lead_data JSON column.
`list_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

changedInput schema / required

Previous value: -[
-  "list_id"
-]New value: +[
+  "list_id",
+  "format"
+]

First observedOct 31, 2026

TDQS

A3.9/5.0

Behavior5/5

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

The description adds substantial behavior beyond the annotations: private link generation, 100,000-contact limit, automatic page streaming, no extra credit use, 15-minute link expiration, access revocation, and instructions to give the link to the user or download it. This is rich behavioral context for an annotated read-only tool.

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 front-loaded with the core action and mostly avoids waste. It is somewhat longer than necessary but each detail about the link and file output is useful.

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?

With no output schema, the description adequately explains the key return artifact: a private download link with expiration behavior. It covers the important export semantics, though list_id remains undocumented.

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 only 33%, so the description must compensate. It clarifies file formats and that columns support nested lead_data fields, but it does not explain list_id or add meaning beyond what the schema already says about columns.

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: get a private download link for a complete list as CSV/JSON/JSONL. It is clear what the tool produces, though it does not explicitly distinguish itself from the sibling tool export_list.

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

Usage Guidelines3/5

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

It gives one useful usage cue: 'Prefer this when the user wants a file.' However, it does not name or explain the alternative export_list, nor does it provide when-not-to-use guidance.

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

All Dievio 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?