Skip to main content
Glama

resume_signal

Resume a paused signal and return it. Its first check reports what appeared while it was paused, as far as LinkedIn still shows it; it is not a new baseline. Resuming an active signal changes nothing and succeeds. Fails with signalLimitReached when the account already has the maximum number of active signals of this type (pause or delete one first), with signalStopped for a stopped signal or a postUrl signal whose 30-day watch period has ended, and with signalNotFound for an unknown id.

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": {
      "signalId": "<signalId>"
    },
    "name": "resume_signal"
  }
}

Input Schema

NameRequiredDescriptionDefault
signalIdYesSignal id, as returned by create_signal or get_signals.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only mark it as a non-read-only, open-world mutation; the description adds the genuinely non-obvious behavior that the first check reports what appeared while paused and is explicitly not a new baseline. It also enumerates the three failure modes (signalLimitReached, signalStopped, signalNotFound) including the 30-day postUrl watch expiry.

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 is front-loaded in the first sentence and every subsequent sentence carries actionable information. The error list is packed into one long sentence with nested clauses, which is dense but not padded.

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 one-parameter mutation tool with no output schema, the description covers return behavior, idempotency on already-active signals, capacity semantics, and each terminal failure case. An agent has everything needed to call it correctly and interpret the common errors.

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?

The single parameter is fully documented in the schema (100% coverage), so the baseline is 3. The description adds only validity context by indicating that an unknown id yields signalNotFound, without adding format or sourcing detail beyond what the schema's 'as returned by create_signal or get_signals' already states.

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 ('Resume a paused signal and return it') in the first clause, which cleanly separates it from pause_signal, get_signal, and delete_signal. The added fact that it returns the signal makes the operation's shape unambiguous.

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 concrete preconditions: resuming an active signal is a no-op and succeeds, while a full account requires pausing or deleting a signal first. It stops short of explicitly routing to sibling tools (pause_signal) outside the parenthetical, so a 4 rather than a 5.

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.