Skip to main content
Glama

create_log_export

Define a filtered log export with selected fields for later processing and retrieval; this sets up the export only and requires an Enterprise Portkey plan.

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. Enterprise-gated. Returns 403 on non-Enterprise Portkey plans.

Input Schema

NameRequiredDescriptionDefault
ai_modelNoFilter by specific AI model names
cost_maxNoMaximum cost filter
cost_minNoMinimum cost filter
time_maxYesMaximum time filter in date format (e.g., '2024-01-31' or ISO 8601)
time_minYesMinimum time filter in date format (e.g., '2024-01-01' or ISO 8601)
descriptionNoHuman-readable description for the export job
workspace_idNoWorkspace ID for the export
total_units_maxNoMaximum total units (tokens) filter
total_units_minNoMinimum total units (tokens) filter
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

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.9
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Addedv1.0.1
  3. Removed
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context not in annotations: that creation is a setup-only step with no processing triggered, and that non-Enterprise plans receive a 403. It stops short of covering duplicate-definition behavior or limits, so a 4 rather than 5.

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?

Three short sentences, front-loaded with what the tool does, then the workflow, then the entitlement caveat. Every sentence adds information an agent needs and nothing is repeated from structured fields.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema covers return values, so the description needn't explain them. It supplies exactly what the structured data cannot: the setup-only semantics, the required follow-up call, and the Enterprise entitlement gate. Nothing needed to invoke this correctly is missing.

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 per-field descriptions, so the schema already carries the parameter burden. The description only restates that filters and requested fields exist, adding no syntax or constraint detail beyond the schema — the 3 baseline applies.

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?

States a specific verb and resource ('Create a log export definition with filters and requested fields') and immediately delimits scope: it only sets up the export and does not start processing. That distinguishes it cleanly from siblings start_log_export, get_log_export, and download_log_export.

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 names the next step ('call start_log_export next') and the follow-up alternatives ('get_log_export or download_log_export'), plus the entitlement precondition (Enterprise-gated, 403 otherwise). There is no ambiguity about when to use this versus its siblings.

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