List all profiles owned by the authenticated creator. Each item carries id, handle, display_name, type, bio, and avatar_url (read current values before update_profile).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark this as read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds useful behavioral detail by listing the exact fields returned and cautioning about reading current values before update_profile.
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?
Two short sentences. The first names the action and scope, the second lists return fields plus a practical caution. No filler 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?
For a zero-parameter list endpoint without an output schema, the description supplies enough return shape information and clarifies the ownership scope. It adequately supports correct invocation and interpretation of results.
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 tool has zero parameters, so there is nothing to explain at the parameter level. The description adds useful scope semantics by clarifying the implicit filter: profiles 'owned by the authenticated creator.'
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?
States a specific verb and resource: 'List all profiles owned by the authenticated creator.' This clearly distinguishes it from get_profile (single profile) and update_profile (mutation) among the siblings.
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 makes its use clear: retrieve all profiles owned by the caller. It also gives contextual guidance by noting that current values should be read before calling update_profile, though it doesn't explicitly name alternatives like get_profile for single-profile cases.
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.
Most tools clearly target distinct resources and actions, but there is some overlap: get_profile and get_my_earnings both expose balance/cap information, and list_my_profiles could be confused with get_profile. The descriptions are generally clear enough to avoid serious misselection.
Every tool name follows a consistent snake_case verb_noun pattern: get_product, list_campaigns, submit_post, update_profile, etc. The verbs match the intended actions, and there are no mixed naming conventions or vague style deviations.
Twenty tools is slightly heavy, but the count is reasonable for the scope: the server covers products, campaigns, posts, earnings, profiles, notifications, asset uploads, and AI tool usage/reviews. Each tool serves a recognizable purpose, so the size feels like breadth rather than redundancy.
Core workflows are present—search products, get campaigns, apply, generate tracking links, submit posts, view earnings, manage notifications—but there are notable gaps. There is no way to list past posts or retrieve a post_id except from submit_post, no list of campaign applications, and no tool discovery endpoint for the AI tool slugs used by declare_tool_usage and write_tool_review.
