Check if your YouTube account is connected.
Returns connection status, channel name, and scope information.
Does NOT modify any data or initiate any connections.
Common errors:
- Not connected: use `youfiliate_connect_youtube` to connect.
| Name | Required | Description | Default |
|---|---|---|---|
| params | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description explicitly states 'Does NOT modify any data or initiate any connections,' which adds detail beyond the annotations (readOnlyHint, idempotentHint, destructiveHint). It also describes return values, but no rate limits or other behavioral traits are mentioned. The statement aligns with and reinforces the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and front-loaded with the primary purpose. It uses short, scannable paragraphs for returns and common errors. Every sentence adds value, with no fluff or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple and read-only. The description covers what it does, what it returns, and how to handle the main error case. With an output schema present and annotations covering safety, the description is sufficient for an agent to use the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The only parameter, response_format, is already well-documented in the input schema with a description, default value, and allowed values. The description adds no additional parameter semantics, but since the schema provides full coverage, a baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool checks if a YouTube account is connected, which is a specific verb and resource. It also lists what it returns (connection status, channel name, scope information), distinguishing it from sibling tools like connect/disconnect.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description includes a common error scenario and directs users to an alternative tool ('use youfiliate_connect_youtube to connect') when not connected. This provides clear context for when to use this tool versus the connection tool, though it could explicitly state when to choose this tool over other status-related tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource or action, from smart link CRUD to health checks, statistics, and YouTube migration lifecycle. There is no meaningful overlap; even similar-sounding tools like get_smart_link and get_smart_link_stats are clearly separated by configuration vs. detailed analytics.
All tools follow a consistent verb_noun pattern with a uniform 'youfiliate_' prefix, e.g., create_smart_link, get_smart_link, delete_smart_link, and start_migration. No mixed conventions or exceptions are present.
With 18 tools, the set is slightly larger than the ideal 3-15 range but remains well-scoped for the dual domain of smart link management and YouTube migration. Each tool has a clear purpose, and the count is not excessive given the feature coverage.
The tool surface covers the full smart link lifecycle (create, read, update, delete, list) plus advanced features like health checks, aggregate/per-link stats, and preferences. The YouTube migration workflow is also complete with connect/disconnect, status, preview, start, list, status, and rollback, leaving no obvious dead ends.