Skip to main content
Glama

create_log_export

Create a log export definition with filters and requested fields. Sets up the export configuration for later processing.

Instructions

Create a log export definition with filters and requested fields. This only sets up the export and does not start processing; call start_log_export next, then use get_log_export or download_log_export to inspect or retrieve the finished result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspace_idNoWorkspace ID for the export
descriptionNoHuman-readable description for the export job
time_minYesMinimum time filter in date format (e.g., '2024-01-01' or ISO 8601)
time_maxYesMaximum time filter in date format (e.g., '2024-01-31' or ISO 8601)
cost_minNoMinimum cost filter
cost_maxNoMaximum cost filter
total_units_minNoMinimum total units (tokens) filter
total_units_maxNoMaximum total units (tokens) filter
ai_modelNoFilter by specific AI model names
requested_fieldsYesFields to include in export: id, trace_id, created_at, request, response, is_success, ai_org, ai_model, req_units, res_units, total_units, request_url, cost, cost_currency, response_time, response_status_code, mode, config, prompt_slug, metadata

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool call succeeded and returned structured data
dataNoStructured success payload when ok is true
errorNoStructured error payload when ok is false
Behavior4/5

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

Annotations (non-readOnly, non-destructive) are consistent. The description adds value by explaining that the tool only creates a definition and does not process, preventing assumptions. Could mention if it overwrites existing definitions, but overall good.

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: first states purpose, second gives workflow. No fluff, well-structured, and front-loaded with key information.

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 10 parameters and a multi-step workflow, the description covers the essential context (setup vs. execution). Output schema exists, so return values are handled. Could mention the output includes the export ID, but not critical.

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 100% with each parameter having a description. The tool description mentions 'filters and requested fields' but does not add new meaning beyond the schema. Baseline 3 applies per guidelines.

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 creates a log export definition, not starting processing. It distinguishes itself from siblings like start_log_export, get_log_export, and download_log_export by specifying the workflow order.

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

Usage Guidelines5/5

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

Explicitly tells the agent to use this tool to set up an export, then call start_log_export next, and later use get_log_export or download_log_export. This provides a complete workflow without needing external documentation.

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/s-b-e-n-s-o-n/portkey-admin-mcp'

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