Skip to main content
Glama

Quote a creator profile

quote_creator_profile
Read-only

Quote the credits a video start will hold and charge for an Instagram or TikTok profile, reel, or video link; returns 0 when a recent profile can answer.

Instructions

Price analyze_creator for a source_url before starting it: credits_estimate is what a start holds and charges once it succeeds (20), 0 when a profile from the last hour would answer (replays_profile_id): one of the same link, or of the creator a handle link names. A reel or short link not seen before quotes the full price, since its author is not known until the start reads it. A YouTube or unknown link is refused here too. Free; starts nothing.

Input Schema

NameRequiredDescriptionDefault
source_urlYesan Instagram profile or reel link (instagram.com/<handle>, instagram.com/reel/<code>, /p/<code>) or a TikTok profile or video link (tiktok.com/@<handle>,…

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.39.0

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description explains credit behavior: a start holds and charges 20 on success, but 0 when a recent profile can replay. It also discloses refusal cases and that the tool starts nothing.

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 is front-loaded and every sentence contributes pricing, replay, or refusal detail. The nested colons and parentheticals make it denser than ideal, but it is not padded.

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

Completeness4/5

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

For a one-parameter quote tool with no output schema, the description covers the essential behavior: price, free/non-starting nature, replay discount, and refusal conditions. It explains the key return concepts without needing to spell out a full response shape.

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 already 100%, so the schema documents the source_url format. The description still adds useful meaning by explaining replay handling and that a new reel or short link quotes full price because its author is unknown until the start reads it.

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?

The description states a specific verb and resource: it prices analyze_creator for a source_url before starting it. It also distinguishes this tool from the actual analysis start by emphasizing that it is free and starts nothing.

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?

It clearly says to use this before starting analyze_creator and notes that YouTube or unknown links are refused. It does not explicitly compare against other quote siblings such as quote_analysis, but the intended timing is clear.

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