Skip to main content
Glama
sassoftware

SAS MCP Server

Official
by sassoftware

export_report

Export a Visual Analytics report or selected objects in package, PDF, PNG, SVG, CSV, TSV, XLSX, or summary format. Use rendering options for PDF and image size for images.

Instructions

Export a Visual Analytics report (or specific report objects) in any format the VA service exposes, via its synchronous export endpoints.

Formats (export_format):

  • package — full report bundle as a .zip (source files, query results, and rendered content); whole report or selected objects.

  • pdf — rendered PDF; whole report or selected objects. Pass rendering overrides (e.g. orientation, paperSize, margin, includeCoverPage) via options.

  • png / svg — image of the report or a single object; image_size is required, e.g. "1200px,800px".

  • csv / tsv / xlsx — the data behind a single report object; exactly one object label is required.

  • summary — the report's text summary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
optionsNoOptional ``pdf`` rendering overrides, passed through as query parameters (e.g. ``{"orientation": "landscape"}``).
report_idYesID of the report.
image_sizeNoRequired for ``png``/``svg``; format ``"<w>px,<h>px"``.
export_formatYesOne of package, pdf, png, svg, csv, tsv, xlsx, summary.
report_objectsNoReport object labels to export. ``package``/``pdf`` accept several; image and data formats accept exactly one; ``summary`` accepts none. Omit to export the whole report where the format allows it.
Behavior4/5

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

Despite no annotations, the description discloses synchronous behavior, format-specific requirements (e.g., image_size for png/svg), and constraints (e.g., exactly one object for data formats). It does not mention side effects or permissions but is generally transparent.

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 well-structured with bullet points, front-loading the main purpose and then detailing each format. It is not overly verbose; every sentence contributes useful information.

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?

The description does not specify the output format (stream vs URL) or clarify the response type. Given the tool exports files, this is a gap. Sibling differentiation could also be improved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds value by providing format examples, constraints on report_objects per format, and formatted examples for image_size. This goes beyond the basic schema descriptions.

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 clearly states the tool exports Visual Analytics reports or objects in multiple formats. It lists all supported formats with details, distinguishing it from siblings like get_report or file operations.

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?

The description implies usage for export but does not explicitly state when to use this tool versus alternatives (e.g., get_report). No 'use this when' or 'not for' guidance is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sassoftware/sas-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server