Skip to main content
Glama
Sign In

Tokfluence

by com.tokfluence
OverviewDiscussionsAdmin

Pause or resume a crawl

pause_seed_campaign
Idempotent

Stops a running crawl, or resumes a paused one. Pausing frees a slot against the 3-campaign limit and stops the spend; everything already discovered stays in the index.

Pause a campaign whose inNiche is not keeping up with scraped: it is burning capacity on the wrong crowd, and a fresh campaign with better keywords will do better than letting it run.

Free. Resuming does not cost the create charge again.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "pause_seed_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
resumeNotrue resumes a paused campaign. Default false, which pauses it.
campaign_idYesId of a campaign on this account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare the safety profile (non-read-only, non-destructive, idempotent, open-world). The description adds genuinely new behavior: pausing frees a slot against the 3-campaign limit, halts spend, preserves everything already discovered in the index, and resuming does not re-charge the create fee. These are exactly the side effects an agent needs before calling a mutation tool.

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 action is front-loaded in the first sentence, followed by consequences and then the decision heuristic. Every sentence carries information; the only blemish is awkward mid-sentence line wrapping that fragments '3-campaign limit and stops the spend.'

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 simple two-parameter toggle with no output schema, the description covers action, capacity effects, cost, data retention, and a usage heuristic. Nothing an agent needs in order to choose or invoke 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 coverage is 100%, so both campaign_id and the resume flag are fully documented in the schema itself. The description reinforces the resume direction and its cost implication but adds no format or validation detail beyond the schema, so the baseline 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 and resource in both directions: 'Stops a running crawl, or resumes a paused one.' An agent can immediately separate this from create_seed_campaign, get_seed_campaign, and list_seed_campaigns without opening any schema.

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 a concrete diagnostic for when to pause ('inNiche is not keeping up with scraped') and points toward an alternative action (start a fresh campaign with better keywords instead of letting it run). It stops short of stating when not to pause or when to prefer resume over create, so it is clear context rather than full when/when-not guidance.

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

All Tokfluence 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