Skip to main content
Glama
Sign In

Tokfluence

by com.tokfluence
OverviewDiscussionsAdmin

Add creators to a list

add_creators_to_list
Idempotent

Adds creators to one of this account's lists, by tkc_* id or TikTok username.

Safe to replay: creators already on the list are skipped rather than duplicated, so a partially-applied batch can simply be sent again. Insertion order becomes the list's "date added" order, so send your best matches first and the client sees them first.

Up to 500 creators per call. Handles the index has never seen come back in unresolved rather than failing the whole batch; find those with search_creators or get_creator first, which caches them.

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": {
      "list_id": "<list_id>",
      "creators": "<creators>"
    },
    "name": "add_creators_to_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentNoOptional note applied to every creator added in this call, e.g. why they matched.
list_idYesId of a list on this account, from create_list or list_lists.
creatorsYestkc_* ids or TikTok usernames, best matches first. Max 500.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: replay safety and why (duplicates skipped), insertion-order semantics becoming 'date added' order, a 500-per-call limit, partial-batch behavior returning `unresolved` instead of failing, and a cost signal ('Free'). These are behaviors an agent cannot infer from idempotentHint/destructiveHint alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then paragraph-by-paragraph on replay safety, ordering, batch limits, and cost. Every sentence carries distinct operational information; even the terse 'Free.' earns its place as a cost signal.

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 `unresolved` return field and its meaning, plus the partial-success model. For a 3-parameter mutation tool with no nested objects, nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: `creators` ordering matters because insertion order defines 'date added' order, and the effective maximum of 500 per call. The `comment` parameter is left to the schema, but overall it adds value above the schema.

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 ('Adds creators to one of this account's lists') and immediately narrows the accepted identifier forms (tkc_* id or TikTok username). This is clearly distinguishable from create_list, plan_creator_list, and search_creators.

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 recovery guidance for unresolved items: 'find those with search_creators or get_creator first, which caches them,' which explicitly names the sibling tools and the condition that selects them. It lacks an explicit statement of when not to use this tool (e.g. versus plan_creator_list), keeping it short of a 5.

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