Skip to main content
Glama

Audora

by music.audora
OverviewDiscussionsAdmin

Look the artist up online

find_online

Runs Audora's own lookup of what the artist has already published (streaming profiles, releases, their site and social profiles), or reads where one is and what it found. Use it only when you cannot search the web yourself: otherwise look the artist up with your own search, check with them that you found the right artist, and fill their page with update_profile. With action "start" it begins one, which takes 1–2 minutes; the artist gets a few a day, shared with Soundcheck in Audora. The account's first lookup is free and each later one costs credits and needs the artist's spend permission: start with dry_run: true to read the price, tell the artist, then start with confirm_cost_credits. With action "status" (the default) it reads the newest lookup, or the one named by run_id. Every fact comes with the pages it was read on. It never changes the artist's profile: when it is done, call propose_profile so the artist keeps what is theirs in Audora.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkNoFor start: one page the artist is on (Apple Music, Deezer, SoundCloud, YouTube, Bandcamp, their site, Instagram), as a full https:// address. It is the best starting point. A Spotify link is kept as theirs but never opened, so another page starts the lookup better.
actionNo"start" a new lookup, or read its "status". Default: status.
artistNoOnly when you are connected as a label: the roster artist this call is for — their artist_user_id from list_roster, or their exact artist name. Required for every artist tool on a label connection. Leave it out on an artist's own connection.
not_meNoFor start: names of earlier matches the artist said are not them.
run_idNoFor status: a particular lookup. Default: the newest.
dry_runNoFor start: true to read what the lookup costs without starting it.
confirm_cost_creditsNoFor start: the price a dry run quoted and you told the artist. Needed for a lookup that is not free.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / confirm_cost_credits
      Added value: +{
+  "description": "For start: the price a dry run quoted and you told the artist. Needed for a lookup that is not free.",
+  "type": "number"
+}
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "For start: true to read what the lookup costs without starting it.",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / link / description
      Previous value: -"For start: one page the artist is on (Spotify, Apple Music, Deezer, SoundCloud, YouTube, Bandcamp, their site, Instagram), as a full https:// address. It is the best starting point."New value: +"For start: one page the artist is on (Apple Music, Deezer, SoundCloud, YouTube, Bandcamp, their site, Instagram), as a full https:// address. It is the best starting point. A Spotify link is kept as theirs but never opened, so another page starts the lookup better."
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: 1–2 minute duration, a per-artist daily cap shared with Soundcheck, first-lookup-free pricing, credit cost plus the artist's spend permission, and the fact that every returned fact carries its source pages. It also states it never mutates the profile, consistent with readOnlyHint=false (which reflects credit/state mutation, not profile writes) and destructiveHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then usage, cost, and status handling in a logical order, and every sentence carries distinct information. It is long and clause-heavy for a single paragraph, with minor editorial padding ('so the artist keeps what is theirs in Audora'), but nothing is truly redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description covers the return contract ('every fact comes with the pages it was read on'), the async nature (1–2 minutes, status action), the pricing/permission flow, and the correct post-call handoff. An agent has everything needed to invoke both actions correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds workflow meaning the schema cannot: the dry_run → confirm_cost_credits sequencing, the default of 'status', and that status reads the newest run unless run_id names one. The link and not_me semantics live mostly in the schema, so it does not fully re-explain every parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — running Audora's own artist lookup and reading its result — and distinguishes itself from siblings by naming update_profile (filling the page) and propose_profile (post-lookup handoff). It also carves out the 'do your own web search instead' case. The dual start/status nature makes the opening sentence slightly dense, but an agent can tell what this does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use ('only when you cannot search the web yourself'), the alternative ('look the artist up with your own search... fill their page with update_profile'), and the required follow-up after completion ('call propose_profile'). It also spells out the conditional cost workflow: dry_run to read the price, tell the artist, then start with confirm_cost_credits.

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

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