Skip to main content
Glama

create_log_export

Creates a filtered log export definition for Enterprise Portkey plans, setting time range and requested fields without starting processing; call start_log_export next to begin.

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.

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": {
      "time_min": "<time_min>",
      "time_max": "<time_max>",
      "requested_fields": "<requested_fields>"
    },
    "name": "create_log_export"
  }
}

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
okYesCall succeeded
dataNoSuccess payload
errorNoFailure details

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.16.5
    • changedOutput schema / properties / data / description
      Previous value: -"Structured success payload when ok is true"New value: +"Success payload"
    • changedOutput schema / properties / error / description
      Previous value: -"Structured error payload when ok is false"New value: +"Failure details"
    • changedOutput schema / properties / error / properties / details / description
      Previous value: -"Optional structured error details"New value: +"Extra error details"
    • changedOutput schema / properties / error / properties / message / description
      Previous value: -"Human-readable error message"New value: +"Error message"
    • changedOutput schema / properties / ok / description
      Previous value: -"Whether the tool call succeeded and returned structured data"New value: +"Call succeeded"
  2. 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"
  3. Addedv1.0.1
  4. Removed
  5. 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 this is a non-read-only, non-destructive, non-idempotent, open-world write. The description adds genuinely new behavior: the call is a two-step async setup that does not begin processing, and non-Enterprise plans get a 403. It stops short of describing what the created definition returns or any limits on export size, so a 4 rather than a 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 compact sentences: what it does first, the workflow consequence second, the access constraint third. Nothing is redundant and the most important caveat (does not start processing) is front-loaded.

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?

For a 10-parameter async setup tool with an output schema present, the description covers purpose, sequencing, the follow-up alternatives, and the access gate. An agent has everything needed to decide and call correctly without needing return-value documentation.

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%, with every filter, requested_fields, workspace_id, and description documented in the schema itself. The description only summarizes 'filters and requested fields' and adds no format, default, or constraint detail beyond what the schema already supplies, so the baseline of 3 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 (create) and resource (log export definition) plus the scope (filters and requested fields). It explicitly separates itself from start_log_export, get_log_export, and download_log_export, so an agent can place it in the workflow without opening schemas.

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?

Gives explicit sequencing: this tool only creates the definition, then call start_log_export, then get_log_export or download_log_export to inspect or retrieve results. It also states the Enterprise gating prerequisite and the 403 failure mode for non-Enterprise plans.

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