Skip to main content
Glama

Get agent details

get_agent_details
Read-only

list_agents returns only one-line summaries — call this to get the full picture for a specific agent. Run-level history is returned here as recent_runs; each entry carries its run id, which you pass to get_run_transcript for that run's full tool-by-tool transcript. Agent-specific operational learnings are returned as a top-level learnings list (managed via append_learning). Dict with agent fields, workspace, learnings, recent_runs, recent_runs_truncated (True when older runs remain past this page of recent_runs), and tracking_summary. When the agent has prospects, tracking_summary.funnel carries the derived outreach rollup the agent workspace shows — per-channel funnels, connection acceptance_rate, reply_rate, and the people-level lead_funnel — so read rates and lead buckets from there rather than deriving them off the raw stage counts. lead_funnel.reached holds the numbers on the funnel's rungs (per rung, everyone who got at least that far), except reached.accepted: the people who accepted a connection request this agent sent them, out of lead_funnel.invited, the people it sent one, as lead_funnel.accept_rate. lead_funnel.rates {accepted of invited; replied, interested, meeting_booked of contacted} and lead_funnel.step_rates {interested of replied, meeting_booked of interested} hold whole percents, null where the base is 0. lead_funnel.targets holds the LinkedIn target for each rates key, as a whole percent of the same base, each value null where it doesn't apply: accepted when no connection request went out, the others when anyone in the funnel is on email or nobody is on LinkedIn. The lead_funnel's other stage keys count each person once, at their furthest stage, so together they add up to lead_funnel.prospects. lead_funnel.removed counts the people removed from the campaign, who stay at the stage they reached, so it overlaps those keys; list_people with the agent_id and a "removed" filter of 'removed' lists them. mcp_changes lists changes made outside Sliq by the user's or a teammate's MCP clients (such as Claude) calling Sliq tools directly, newest first, one entry per burst of calls to one tool: id, tool_name, client_label (with the teammate's email when a teammate made it), count, first_at, last_at, and latest_arguments (the burst's latest call's arguments). Pass an entry's id as change_id to get_mcp_change_calls to read every call in the burst.

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": {
      "agent_id": "<agent_id>"
    },
    "name": "get_agent_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesID of the agent to load
on_behalf_ofNoA teammate's email, or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account.
recent_runs_limitNoHow many of the most recent runs to include (default 10, max 50)
recent_runs_offsetNoRuns to skip for paging the recent_runs list (default 0). When `recent_runs_truncated` is True, re-call with recent_runs_offset += recent_runs_limit to page into older runs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / on_behalf_of / description
      Previous value: -"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."New value: +"A teammate's email, or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
  2. 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."
      +}
  3. Changed3 schema fields changed
    • addedInput schema / properties / agent_id
      Added value: +{
      +  "description": "ID of the agent to load",
      +  "type": "integer"
      +}
    • removedInput schema / properties / task_id
      Removed value: -{
      -  "description": "ID of the task to load",
      -  "type": "integer"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "task_id"
      -]New value: +[
      +  "agent_id"
      +]
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, so the description carries the rest and it does: it discloses returned sections, the recent_runs_truncated paging signal, that lead_funnel keys are mutually exclusive except lead_funnel.removed, and that mcp_changes is ordered newest-first per call burst. That is behavior beyond what the read-only hint supplies.

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 summary is front-loaded with purpose before the alternative-tool routing, and every sentence is on-topic. The returns block, however, is unusually long and drills into derived-rate derivation rules for lead_funnel, which is dense detail an agent must wade through to reach the operational guidance.

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, so the description must explain the return shape and it does so comprehensively, including truncation, paging, and cross-tool handoffs. For a four-parameter read tool on a complex agent object, nothing an agent needs to call or interpret it 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 description coverage is 100%, so the baseline applies. The description reinforces agent_id's meaning and ties recent_runs to paging, but it adds no new semantics for on_behalf_of or the offset/limit behavior beyond what the schema already documents.

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 ('Load full details for a single agent') and enumerates the payload: workspace, learnings, recent runs, tracking summary. It explicitly contrasts with 'list_agents returns only one-line summaries', so an agent can distinguish this from the sibling without opening either schema.

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 concrete trigger conditions: 'when the user asks about a specific agent's progress, history ("what happened with X yesterday"), or contents.' It also names the alternative (list_agents) and the condition that selects this tool instead, then routes onward to get_run_transcript and append_learning for adjacent needs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources