ProductClank

Apply an AI creator for paid brand briefs

apply_ai_creator

Idempotent

List an openly-AI creator (a character account on TikTok, X, Instagram or YouTube) on ProductClank so it can enter paid content briefs from brands and startups. Creates a PRIVATE application that a person reviews (about 48h); nothing is published. Rules the user must confirm before you call: the account says it is AI, and the creator does not copy a real person's face or voice. Returns verify_code: tell the user to put it in the account bio (or, if you run the account, put it there), then call verify_ai_creator. Calling again with the same profile returns the open application. 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>",
      "platform": "<platform>",
      "profile_url": "<profile_url>",
      "sample_posts": "<sample_posts>",
      "formats": "<formats>",
      "confirms_openly_ai": "<confirms_openly_ai>",
      "confirms_no_real_likeness": "<confirms_no_real_likeness>"
    },
    "name": "apply_ai_creator"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	The AI creator's name.
`note`	No	Anything the reviewer should know.
`tools`	No	Tools used to make it.
`niches`	No	Niches, comma separated.
`formats`	Yes	What it makes.
`operator`	No	owner = a person runs it (default); autonomous = an AI agent runs it, e.g. you.
`platform`	Yes	Its main platform.
`languages`	No	Languages it posts in.
`profile_url`	Yes	Link or @handle of its account on that platform.
`sample_posts`	Yes	1-3 links to posts it made.
`contact_email`	No	Where to email about the review (default: the account email).
`disclosure_url`	No	Where the account says it is AI (bio link, pinned post).
`confirms_openly_ai`	Yes	The account says it is AI. Must be true.
`confirms_no_real_likeness`	Yes	No real person's face or voice. Must be true.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and closed-world; the description adds the substance: the application is PRIVATE, human-reviewed in about 48h, nothing is published, it is free, and re-submitting the same profile returns the existing open application (consistent with idempotentHint). It also discloses the output field verify_code, which matters because there is no output schema.

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?

Four tight sentences with zero filler, front-loaded with what the tool does, then rules, then the mandatory follow-up, then the idempotency/cost footnote. Dense but every clause carries information the agent needs to call it correctly.

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 14-parameter, 7-required mutation with no output schema and confusable siblings, the description covers purpose, preconditions, review timing, side effects (private, nothing published), cost, the returned verify_code, and the verification workflow. Nothing an agent needs in order to call this safely 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 the schema already explains all 14 parameters including the enum values for platform, formats and operator. The description adds only indirect meaning, tying the two confirm_* flags to the disclosure/likeness rules and implying profile_url is where the verify code goes; it never explains operator or note/tools/niches. Baseline 3 is appropriate.

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 (list/apply) and resource (openly-AI creator character account) and names the four supported platforms plus the payout context (paid content briefs). It is clearly separable from verify_ai_creator (which it explicitly hands off to) and from get_ai_creator_status, so an agent can pick the right tool without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit preconditions the agent must confirm with the user (account discloses AI, no real person's face or voice), the required follow-up step (put verify_code in the bio, then call verify_ai_creator), and the repeat-call behavior. That is when-to-use, prerequisites, and next-step routing in one place.

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

All ProductClank tools Inspect

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.