Skip to main content
Glama
Sign In

Linked API

by io.github.Linked-API
OverviewDiscussionsAdmin

manage_conversation

Archive, star, or mute a conversation thread by threadId (st.manageConversation action). Provide the threadId as returned by get_inbox and the operation to perform.

Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingReason, workflowId, operationName, message}. To retrieve the final result, call get_workflow_result with the returned workflowId and operationName — it will long-poll until completion or the request budget elapses, then return either the final result or another in-progress snapshot. Do not retry the original tool while a workflow is still running; that creates duplicate queued work.

A pending workflow carries pendingReason: 'queued' means it is waiting its turn behind other work on the same account and will start within minutes. 'outsideWorkingHours' means the account has configured working hours and the workflow is parked until they reopen — possibly the next working day. In that case get_workflow_result returns immediately instead of polling, message states when the window opens, and you should report that to the user rather than looping.

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": {
      "threadId": "<threadId>",
      "operation": "<operation>"
    },
    "name": "manage_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
threadIdYesConversation thread identifier, as returned by get_inbox.
operationYesOperation to perform on the conversation thread.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true) by disclosing that the action is queued into a cloud-browser workflow, can take several minutes, and returns immediately with a pending/running snapshot. It spells out the pendingReason semantics, the duplicate-work risk of retrying, and the split responsibility with get_workflow_result — exactly the behavior an agent needs before calling a slow mutation.

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?

Purpose and required inputs are front-loaded in the first sentence, followed by the async/follow-up contract. It is on the long side, but the length is driven by genuinely necessary workflow semantics rather than filler; the pendingReason explanation could be tightened without losing meaning.

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 describe the return contract — and it does, naming the exact fields (status, pendingReason, workflowId, operationName, message) and the handoff to get_workflow_result. For a slow, queued mutation with two required params, nothing an agent needs 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% and both parameters are documented, including an enum for operation, so the schema carries most of the load. The description adds only the provenance hint that threadId comes from get_inbox, which is the baseline expectation rather than new semantic depth.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb set (archive, star, mute) against a specific resource (conversation thread) keyed by threadId, which lets an agent match intent quickly. It does not distinguish itself from the near-identically named sibling nv_manage_conversation, so an agent still cannot confidently pick between the two from this text alone.

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

Usage Guidelines4/5

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

Gives explicit operational guidance: use threadId as returned by get_inbox, then call get_workflow_result with the returned workflowId and operationName rather than retrying the original tool. It also tells the agent what to do when pendingReason is 'outsideWorkingHours' (report the window to the user, don't loop). The only gap is no guidance on when to prefer this over nv_manage_conversation or direct send_message-style siblings.

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

All Linked API 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