Skip to main content
Glama

Export csv

export_csv
Read-onlyIdempotent

Export as CSV text for analysis: messages, deliveries, events, opt_outs, webhook_deliveries, usage, usage_monthly, audit_log or credit_history. At most 50,000 rows; narrow the date range with from and to.

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": {
      "kind": "<kind>"
    },
    "name": "export_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNomessages: body/failure text; events: id/payload text
okNowebhook_deliveries
toNoInclusive; a bare date means the end of that day (UTC)
fromNoISO date/time or epoch ms (messages, deliveries, events, webhook_deliveries)
kindYesmessages, deliveries, events, opt_outs, webhook_deliveries, usage, usage_monthly, audit_log or credit_history
typeNoevents, webhook_deliveries
actorNoaudit_log: actor id or part of the actor email
batchNomessages, deliveries: batch id (bc_...)
actionNoaudit_log: one action, or a group prefix with a trailing dot (team.)
monthsNousage: daily rows for the last N months
numberNomessages, deliveries: digits matched against either side
statusNomessages, deliveries
directionNomessages
to_numberNomessages, deliveries: exact recipient (E.164). `to`/`from` are the date range here.
customer_idNomessages, deliveries
endpoint_idNowebhook_deliveries (default: all endpoints)
from_numberNomessages, deliveries: exact sender (E.164)
target_typeNoaudit_log
failure_codeNomessages, deliveries: failed for this reason (the `failure.code` on a message)
created_afterNoaudit_log: same as on GET /audit-logs (from is accepted too)
blocked_reasonNomessages, deliveries: blocked messages with this reason
created_beforeNoaudit_log: same as on GET /audit-logs (to is accepted too)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / failure_code / enum
      Previous value: -[
      -  "carrier_filtered",
      -  "unreachable",
      -  "invalid_number",
      -  "opted_out",
      -  "campaign_mismatch",
      -  "content_blocked",
      -  "screen_unavailable",
      -  "rate_limited",
      -  "landline",
      -  "carrier_rejected",
      -  "spend_limit_reached",
      -  "insufficient_credits",
      -  "billing_required",
      -  "sender_not_registered",
      -  "quiet_hours",
      -  "consent_required",
      -  "reconfirmation_pending",
      -  "reconfirmation_expired",
      -  "held_for_review",
      -  "review_rejected",
      -  "review_expired",
      -  "campaign_paused",
      -  "sender_rotation",
      -  "recipient_not_verified",
      -  "quota_exceeded",
      -  "destination_not_allowed",
      -  "account_closed",
      -  "account_suspended",
      -  "account_paused",
      -  "topic_unsubscribed",
      -  "unknown"
      -]New value: +[
      +  "carrier_filtered",
      +  "unreachable",
      +  "invalid_number",
      +  "opted_out",
      +  "campaign_mismatch",
      +  "content_blocked",
      +  "screen_unavailable",
      +  "rate_limited",
      +  "landline",
      +  "carrier_rejected",
      +  "spend_limit_reached",
      +  "insufficient_credits",
      +  "billing_required",
      +  "sender_not_registered",
      +  "quiet_hours",
      +  "consent_required",
      +  "reconfirmation_pending",
      +  "reconfirmation_expired",
      +  "held_for_review",
      +  "review_rejected",
      +  "review_expired",
      +  "campaign_paused",
      +  "sender_rotation",
      +  "recipient_not_verified",
      +  "quota_exceeded",
      +  "destination_not_allowed",
      +  "voip_number",
      +  "toll_free_destination",
      +  "toll_free_unverified",
      +  "account_closed",
      +  "account_suspended",
      +  "account_paused",
      +  "topic_unsubscribed",
      +  "unknown"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / failure_code / enum
      Previous value: -[
      -  "carrier_filtered",
      -  "unreachable",
      -  "invalid_number",
      -  "opted_out",
      -  "campaign_mismatch",
      -  "content_blocked",
      -  "screen_unavailable",
      -  "rate_limited",
      -  "landline",
      -  "carrier_rejected",
      -  "spend_limit_reached",
      -  "insufficient_credits",
      -  "sender_not_registered",
      -  "quiet_hours",
      -  "consent_required",
      -  "reconfirmation_pending",
      -  "reconfirmation_expired",
      -  "held_for_review",
      -  "review_rejected",
      -  "review_expired",
      -  "campaign_paused",
      -  "sender_rotation",
      -  "recipient_not_verified",
      -  "quota_exceeded",
      -  "destination_not_allowed",
      -  "account_closed",
      -  "account_suspended",
      -  "account_paused",
      -  "topic_unsubscribed",
      -  "unknown"
      -]New value: +[
      +  "carrier_filtered",
      +  "unreachable",
      +  "invalid_number",
      +  "opted_out",
      +  "campaign_mismatch",
      +  "content_blocked",
      +  "screen_unavailable",
      +  "rate_limited",
      +  "landline",
      +  "carrier_rejected",
      +  "spend_limit_reached",
      +  "insufficient_credits",
      +  "billing_required",
      +  "sender_not_registered",
      +  "quiet_hours",
      +  "consent_required",
      +  "reconfirmation_pending",
      +  "reconfirmation_expired",
      +  "held_for_review",
      +  "review_rejected",
      +  "review_expired",
      +  "campaign_paused",
      +  "sender_rotation",
      +  "recipient_not_verified",
      +  "quota_exceeded",
      +  "destination_not_allowed",
      +  "account_closed",
      +  "account_suspended",
      +  "account_paused",
      +  "topic_unsubscribed",
      +  "unknown"
      +]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds valuable context beyond annotations: the output is CSV text, the row cap is 50,000, and from/to should be used to narrow the range. It still does not cover authorization requirements or per-kind constraints.

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?

Two sentences, front-loaded with the purpose and output format, then the row limit and date-range guidance. The kind enumeration is compact and no sentence is wasted.

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?

For a tool with 22 parameters, 100% schema coverage, and annotations covering safety, the description supplies the key missing behavioral facts: CSV text output and the 50,000-row limit. It could be more complete by distinguishing this tool from export_consent/export_numbers and clarifying that filters vary by dataset.

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 100%, so the baseline is 3. The description mentions kind values and from/to date narrowing, but those details are already fully specified in the schema and it adds no further meaning for the other 20 parameters.

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 uses a specific verb and output format ('Export as CSV text') and enumerates the supported datasets. It distinguishes export from the many list_* siblings, but does not mention the closer export_consent or export_numbers siblings.

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 implies bulk extraction 'for analysis' and advises narrowing the date range, but gives no explicit guidance on when to use this instead of list_messages, list_events, get_usage, export_consent, or export_numbers. The context is clear enough to infer, but alternatives are not addressed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.