Skip to main content
Glama

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Get Run Transcript

get_run_transcript
Read-only

Use this when a run's one-line summary isn't enough (e.g. "why did you skip person X in that run?"). Get a run's id from get_agent_details — each entry in its recent_runs list carries one; this returns the same message parts the web Activity tab renders for that run.

The transcript is paginated over its message parts — a heavy run records many. Page with offset while has_more is true. Dict with run_id, the run's summary message + details, status ('completed'/'failed'), created_at, total_messages (parts in the whole run), returned_messages (parts in this page), offset, has_more, and a messages array (role, content or tool_name/args, created_at) sliced to [offset, offset+limit). Empty messages and total_messages 0 when the run recorded no audit session (e.g. it failed before the agent started).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax message parts to return (default 100, max 200).
offsetNoNumber of parts to skip from the start of the run (default 0).
run_idYesAn agent-run id — the `id` of a `get_agent_details` `recent_runs` entry (also shown as `(run N)` in the agent's Recent Activity feed).
on_behalf_ofNoAn agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / on_behalf_of
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / run_id / description
      Previous value: -"An agent-run id — the `id` of a `get_agent_details` `recent_runs`\nentry (also shown as `(run N)` in the task's Recent Activity feed)."New value: +"An agent-run id — the `id` of a `get_agent_details` `recent_runs`\nentry (also shown as `(run N)` in the agent's Recent Activity feed)."
  3. Changed1 schema field changed
    • changedInput schema / properties / run_id / description
      Previous value: -"An agent-run id — the `id` of a `get_task_details` `recent_runs`\nentry (also shown as `(run N)` in the task's Recent Activity feed)."New value: +"An agent-run id — the `id` of a `get_agent_details` `recent_runs`\nentry (also shown as `(run N)` in the task's Recent Activity feed)."
  4. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, but the description adds substantial behavioral context: the transcript is paginated over message parts, paging is driven by offset while has_more is true, and it discloses the edge case where total_messages is 0 and messages is empty (run failed before the agent started). This goes well beyond the annotation's safety profile.

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?

Front-loads the one-sentence summary, then usage, then pagination, then returns, using clear section tags. Despite its length, every sentence carries distinct information (when-to-use, id provenance, paging, empty-run behavior) with no repetition.

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?

There is no output schema, but the description fully specifies the return shape (run_id, summary, status, created_at, total_messages, returned_messages, offset, has_more, messages) including the degenerate empty case. Combined with explicit paging guidance, an agent has everything needed to call and consume this tool correctly.

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 description coverage is 100%, so the baseline is 3, but the description adds real meaning: run_id is sourced from get_agent_details' recent_runs (also shown as '(run N)' in the Activity feed), and offset's role in pagination is spelled out. It stops short of explaining limit/on_behalf_of in the prose, relying on the schema for those.

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 ('Read the transcript of one past background agent run — every tool call and reasoning step'). It distinguishes itself from nearby siblings like get_agent_details (summary-level) and get_chat_messages by scoping to a single run's audit session.

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 trigger condition ('when a run's one-line summary isn't enough') and the concrete upstream step to obtain the required id from get_agent_details' recent_runs list. No inference is required to decide when or how to call it.

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

All Sliq toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources