droptrack_get_artist_profileGet the current company artist profile used by the AI artist bio feature, including bio, socials, genres, recent tracks, and recent generated bio jobs.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | No | Structured DropTrack result returned by this tool |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds useful behavioral context beyond annotations: it returns the 'current' company artist profile and indicates that recent generated bio jobs are included, which clarifies data freshness and scope without contradicting 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 a single front-loaded sentence that states the resource, purpose, and contents with minimal waste. Every phrase adds value.
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?
Given the zero-parameter interface, read-only annotations, and presence of an output schema, the description is complete. It identifies the resource type, the feature it supports, and the key data categories returned, leaving no critical gap for an agent to call it 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 tool has zero parameters, so there is no parameter ambiguity to resolve. The description's field list gives useful context about what the returned profile contains, and the schema is fully trivially covered.
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 uses a specific verb and resource: 'Get the current company artist profile' and enumerates the actual content included (bio, socials, genres, recent tracks, recent generated bio jobs). This clearly distinguishes it from sibling tools like droptrack_generate_artist_bio or droptrack_get_label_info.
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 implies usage context by noting the profile is 'used by the AI artist bio feature,' but it does not explicitly say when to choose this tool over related alternatives or when not to use it. Usage is inferable but not directly guided.
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 target distinct resources and actions, but several clusters are easy to confuse: get_track_analysis vs get_track_analytics vs get_track_tags, plus analyze_audio/request_track_tagging/auto_tag_tracks overlap in the audio-analysis/tagging space. The descriptions do help separate them, so careful agents can disambiguate, but the naming alone creates real misselection risk.
All tools share the droptrack_ prefix, use snake_case, and follow a verb-first noun pattern, with list for collections and get for single items. Minor inconsistencies exist—add_contact vs create_contact_list, browse vs list, auto_tag_tracks—but the overall convention is predictable and readable.
At 55 tools this is far beyond the recommended 3-15 range and well over the 25+ threshold. Many tools are near variants of each other, especially company-level vs label-level ads, analytics, and wallet tools, inflating the surface area and making selection harder.
The set covers many domains and some workflows are complete, such as album art generation/polling/acceptance/deletion and track tagging request/poll/apply. However, core lifecycle gaps remain: no update or delete for campaigns, contacts, or contact lists, no playlist mutation tools, and AI press-release/bio workflows end at polling without a save or publish step.