Skip to main content
Glama
Sign In

Tokfluence

by com.tokfluence
OverviewDiscussionsAdmin

Check a crawl's progress

get_seed_campaign
Read-onlyIdempotent

Progress for one crawl: how many tags have been walked, how many creators were discovered, scraped, indexed, and how many landed in the niche. Also returns the frontier, the queue of tags and creators still to crawl, ranked by lift.

stats.indexed is the number that matters: those creators are searchable now. When it starts moving, search_creators for the campaign's keywords will return people it did not return before.

inNiche well below scraped means the seed tags are pulling in the wrong crowd. The fix is better keywords in a new campaign, not waiting longer.

Free, so poll it as often as you like.

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": "get_seed_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYesId returned by create_seed_campaign or list_seed_campaigns.

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?

Beyond the readOnly/idempotent annotations, it discloses that calls are free and safe to poll aggressively, and it pre-empts a common misreading by telling the agent that a low inNiche ratio will not fix itself with time. That is decision-relevant behavior the annotations cannot express.

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?

Front-loaded with purpose and the single metric that matters (stats.indexed), then interpretation guidance. It is on the long side and the field-name fragments in the middle sentence cost a little readability, but no sentence is filler.

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, and the description compensates by naming the key return fields and their meaning, including the frontier queue and how to read the scraped-to-inNiche gap. Nothing an agent needs to interpret progress or choose a next step 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 campaign_id and its provenance (create_seed_campaign or list_seed_campaigns) are already documented in the schema. The description adds no parameter-level detail, so the baseline of 3 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?

Opens with a specific verb+resource: 'Progress for one crawl', and immediately enumerates what is reported (tags walked, creators discovered/scraped/indexed/in-niche) plus the frontier queue. This clearly separates it from siblings like list_seed_campaigns, create_seed_campaign, and pause_seed_campaign.

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 usage context: poll it as often as you like because it is free, and it explains the downstream effect on search_creators once stats.indexed moves. It also prescribes a decision rule (inNiche well below scraped means start a new campaign rather than wait), though it does not explicitly name when to prefer a sibling tool.

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