Skip to main content
Glama

Deezer

by io.github.pipeworx-io

Send Pipeworx Feedback

pipeworx_feedback

Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a claim_token; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNobug = something broke or returned wrong data. feature = a new tool or capability you wish existed. data_gap = data Pipeworx does not currently expose. praise = positive note. other = anything else.
contextNoOptional structured context: which tool, pack, or vertical this relates to.
messageNoYour feedback in plain text. Be specific (which tool, what error, what data was missing). 1-2 sentences typical, 2000 chars max.
claim_tokenNoRead the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / properties / claim_token
      Added value: +{
+  "description": "Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments. Returns the status and, once resolved, what actually changed.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "type",
-  "message"
-]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Despite annotations being minimal (readOnlyHint false), the description discloses key behaviors: filing returns a claim_token, passing it later reads status/changes, rate limit of 5/day, free, and does not count against quota. It also notes that the team reads digests daily, giving the agent a sense of impact and latency. No contradiction with annotations.

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?

The description is longer than a typical tool description but every section serves a clear purpose: definition, usage, exclusions, follow-up mechanism, and policy. It is front-loaded with the core purpose and then expands logically. A slight deduction for the almost-marketing sentence about roadmap influence, which is useful context but not strictly necessary.

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?

For a feedback submission tool with 100% schema coverage and no output schema, the description fully covers what the agent needs: when to use, how to frame feedback, exclusions, token flow, rate limits, and quota impact. The lack of an output schema is mitigated by the description explaining the claim_token return and subsequent retrieval. No gaps remain.

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%, providing parameter descriptions for type, context, message, and claim_token. The description adds value by explaining the claim_token round-trip workflow ('pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed'), which is semantics beyond the schema's generic 'Read the reply...' text. Thus above baseline 3.

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

Purpose5/5

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

The description opens with a specific verb+resource: 'Tell the Pipeworx team something is broken, missing, or needs to exist.' It clearly distinguishes this feedback tool from all sibling tools, which are data retrieval or subscription tools. The subsequent bullet-like enumeration of feedback types (bug, feature/data_gap, praise) reinforces scope.

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?

Explicit guidance is given: 'Use when a tool returns wrong/stale data,' 'when a tool you wish existed,' and 'when something worked surprisingly well.' It also provides an exclusions clause ('ONLY for tools served by this Pipeworx connection') and directs users to file elsewhere for non-Pipeworx tools. This is textbook when-to-use/when-not-to-use guidance.

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

All Deezer toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0
Disambiguation2/5

Many tools overlap in purpose (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research all route queries to structured data), and the set mixes Deezer music tools with an unrelated Pipeworx/Polymarket suite. An agent would struggle to pick the right tool for a given request.

Naming Consistency2/5

Naming is mixed: single-word nouns (album, artist, track, chart), verb_noun snake_case (list_subscriptions, resolve_entity), and verbose multi-concept names (scan_competitor_ai_presence, polymarket_kalshi_spread). No consistent pattern across the set.

Tool Count1/5

37 tools for a server named 'Deezer' is far beyond a music API scope; the overwhelming majority are unrelated data-research, prediction-market, and utility tools. This is an extreme mismatch between the server name and the tool surface.

Completeness2/5

For the Deezer music domain, the surface is incomplete (no playlists, user library, lyrics, or radio), while the many unrelated tools each cover only fragments of their domains. The overall set lacks coherent coverage of any single purpose.

Resources