Skip to main content
Glama
Sign In

Tokfluence

by com.tokfluence
OverviewDiscussionsAdmin

Create a creator list

create_list

Creates an empty creator list on this account. The list is the deliverable: it shows up in the Tokfluence dashboard, can be shared with a link, and is where creators go once you have picked them.

Name it after the brief, not after the search. "Bulgaria live shopping hosts" is useful to a human three weeks later; "search results 3" is not.

Call add_creators_to_list next. Free.

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

Input Schema

NameRequiredDescriptionDefault
nameYesHuman-readable list name. Name it after the brief.
currencyNoISO currency for the cost estimates on this list, e.g. 'USD', 'GBP'. Default USD.
shareableNoMint a public share link so the list can be sent to someone without an account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a non-destructive, non-idempotent write; the description adds real context beyond them — the list surfaces in the dashboard, is link-shareable, and is the container creators are added to later. It does not address duplicate names or what happens if the list is never populated, but the behavioral picture is solid.

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 purpose and next step are front-loaded and the naming example is genuinely useful, though the second paragraph is longer than it needs to be and the trailing 'Free.' fragment reads as an afterthought rather than structured information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a create tool with no output schema, the description never says what comes back — notably the list identifier the agent must carry into add_creators_to_list. That is a meaningful omission for a tool that exists only to be chained.

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 name, currency and shareable are already documented. The naming advice ('name it after the brief, not after the search') reinforces intent but largely restates the schema's own 'Name it after the brief', and currency/shareable are not elaborated in the description.

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 ('Creates an empty creator list on this account') and immediately clarifies the resulting object's role in the workflow, distinguishing it from siblings like list_lists and plan_creator_list.

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?

Explicitly routes the agent forward with 'Call add_creators_to_list next' and notes the call is free. It does not say when to prefer plan_creator_list or whether a list must exist before searching, so the guidance is clear but not exhaustive.

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