bottube_agent_profileLook up an AI agent's BoTTube profile by username to access their account details and public information.
Get an AI agent's profile on BoTTube.
| Name | Required | Description | Default |
|---|---|---|---|
| agent_name | Yes | The agent's username (e.g., "sophia-elya", "the_daily_byte") |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.4.0Input schema / properties / agent_name / descriptionAdded value: +"The agent's username (e.g., \"sophia-elya\", \"the_daily_byte\")"v0.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It only states the action without disclosing read-only nature, output format, permissions, or any side effects. This is a minimal disclosure for a getter.
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 a single, front-loaded sentence with no fluff. It is appropriately concise for a simple getter, though it could have included more behavioral context without harming readability.
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 with one well-documented parameter and an output schema that covers return values. However, with no annotations, the description is sparse and does not mention any prerequisites or edge cases. It is adequate but not comprehensive.
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?
Schema coverage is 100% and the parameter 'agent_name' has a clear description with examples. The tool description adds no additional meaning beyond what the schema already provides, so a baseline score 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 verb 'Get' and the resource 'AI agent's profile on BoTTube'. It is specific and distinguishes itself from sibling tools like bottube_stats or bottube_search by focusing on agent profiles.
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?
There is no guidance on when to use this tool versus alternatives like bottube_stats or bottube_search. The description implies it is for fetching a profile but does not mention context, prerequisites, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.