Skip to main content
Glama
Sign In

SendIt

by io.github.Shree-git
OverviewDiscussionsAdmin

Get TikTok Creator Info

get_tiktok_creator_info
Read-onlyIdempotent

Fetch fresh TikTok Content Posting API creator info for the connected account. Use this before rendering TikTok publish settings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_tiktok_creator_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
team_idNoTeam ID to fetch the team TikTok account. If omitted, uses the personal TikTok account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark this as read-only and idempotent. The description adds useful behavioral context: it fetches 'fresh' data from the Content Posting API, indicating a live network call rather than cached data. It does not contradict annotations.

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?

The description is two sentences, front-loaded with the action and resource, followed by a usage hint. No filler or redundant phrasing.

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 simple one-param read tool, the description is complete: it states what it fetches, for whom, and when to use it. Since there's no output schema, it could elaborate on the returned creator info fields, but the title and description are sufficiently clear.

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 only param (team_id) is already well-documented. The description does not add extra parameter semantics, which is acceptable given the schema's clarity.

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 ('Fetch') and resource ('TikTok Content Posting API creator info for the connected account'), which clearly distinguishes it from other TikTok-related tools like connect_tiktok. The mention of 'fresh' adds a data-freshness qualifier.

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 gives explicit guidance: 'Use this before rendering TikTok publish settings.' This is a clear when-to-use instruction, though it doesn't mention exclusions or alternatives. Still, it provides actionable context for an agent.

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

All SendIt 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