Skip to main content
Glama

export_report_data

Read-only

Exports raw ServiceNow table data as structured JSON for external reports, with filters, field selection, and background job support.

Instructions

Export raw table data as structured JSON for use in external reports

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": {
      "table": "<table>"
    },
    "name": "export_report_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
asyncNoRun as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.
limitNoMax records (default: 100, max: 1000)
queryNoEncoded query filter
tableYesTable to export from
fieldsNoComma-separated fields to include

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • addedInput schema / properties / async
      Added value: +{
      +  "description": "Run as a background job and return a job_id at once. Poll it with get_job. Calls that take longer than about 20 seconds switch to a job on their own.",
      +  "type": "boolean"
      +}
  2. First observedv1.0.2

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds essentially nothing on top. It does not mention the async/background-job behavior, automatic 20-second fallback to a job, export size limits, or authorization needs — all behavioral facts an agent needs before calling a potentially long-running read.

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?

A single front-loaded sentence with the verb and resource first and zero wasted words. It is efficient, though the brevity borders on under-specification given the tool's complexity.

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?

Five parameters, no output schema, and thin annotations mean the description carries real burden, yet it only describes the output format in the vaguest terms. Key facts an agent needs — pagination/limit behavior, the async fallback and job polling path, and what the JSON structure actually contains — are absent from the prose and only partially recoverable from the schema.

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 schema fully documents table, query, fields, limit and async, including the default/max limits and the get_job polling behavior. The description adds no parameter meaning beyond that, which is the baseline case rather than a deficiency.

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?

States a specific verb and resource ("Export raw table data") plus the output format ("structured JSON"), which is clearer than a bare restatement of the name. It implicitly separates itself from report-oriented siblings by specifying *raw table data*, but it never names or contrasts any of them, so sibling differentiation is left to inference.

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?

The only usage cue is the phrase "for use in external reports," which hints at a scenario but gives no when-to-use vs when-not guidance. With siblings like export_properties, export_update_set, aggregate_report and generate_report present, an agent gets no help choosing between raw table export and those alternatives, and no prerequisites (permissions, data source selection) are stated.

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