Skip to main content
Glama

Music360 MCP

by br.com.music360.app
OverviewDiscussionsAdmin

music360_list_produto_fonografico

Lista registros de produto fonográfico do tenant atual. Use esta tool para álbuns, singles, EPs e pedidos sobre lançamento musical mais recente. Por padrão retorna apenas lançamentos já disponíveis; use release_scope=all para incluir Produzindo, Agendado futuro, Rascunho ou Takedown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
searchNo
order_byNoCampo para ordenacao (ex.: data_lancamento/lancamento, nome, atualizacao, criacao). Para produto fonografico, "lancamento" e "mais recente" significam data_lancamento. Quando omitido, usa ordenacao padrao da entidade.
per_pageNo
order_dirNoDirecao da ordenacao: ASC crescente, DESC decrescente (padrao).
release_scopeNoEscopo de lançamento. released (padrão): somente produtos disponíveis/lançados. upcoming: próximos lançamentos ainda não disponíveis. all: inclui Produzindo, Agendado, Rascunho, Takedown e Lançado.
released_onlyNoCompatibilidade: true equivale a release_scope=released; false equivale a release_scope=all. Prefira release_scope.
response_profileNoPerfil de resposta. Listagens usam summary por padrão; sensitive exige admin.
sensitive_access_purposeNoFinalidade operacional obrigatória quando response_profile=sensitive ou include_sensitive_details=true.
include_sensitive_detailsNoRetorna detalhes sensíveis mínimos quando autorizado por escopo admin. Padrão: false.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesResultado paginado.
successYesIndica se a operacao foi bem-sucedida.
entity_typeYesTipo da entidade consultada.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / include_sensitive_details
      Added value: +{
+  "description": "Retorna detalhes sensíveis mínimos quando autorizado por escopo admin. Padrão: false.",
+  "type": "boolean"
+}
    • addedInput schema / properties / response_profile
      Added value: +{
+  "description": "Perfil de resposta. Listagens usam summary por padrão; sensitive exige admin.",
+  "enum": [
+    "summary",
+    "standard",
+    "sensitive"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / sensitive_access_purpose
      Added value: +{
+  "description": "Finalidade operacional obrigatória quando response_profile=sensitive ou include_sensitive_details=true.",
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Resultado paginado.",
+      "properties": {
+        "data": {
+          "description": "Lista de registros encontrados.",
+          "items": {
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "page": {
+          "type": "integer"
+        },
+        "per_page": {
+          "type": "integer"
+        },
+        "total": {
+          "type": "integer"
+        },
+        "total_pages": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "data",
+        "total",
+        "page",
+        "per_page",
+        "total_pages"
+      ],
+      "type": "object"
+    },
+    "entity_type": {
+      "description": "Tipo da entidade consultada.",
+      "type": "string"
+    },
+    "success": {
+      "description": "Indica se a operacao foi bem-sucedida.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "entity_type",
+    "data"
+  ],
+  "type": "object"
+}
  2. Changed3 schema fields changed
    • changedInput schema / properties / order_by / description
      Previous value: -"Campo para ordenacao (ex.: data_lancamento, nome, atualizacao, criacao). Quando omitido, usa ordenacao padrao da entidade."New value: +"Campo para ordenacao (ex.: data_lancamento/lancamento, nome, atualizacao, criacao). Para produto fonografico, \"lancamento\" e \"mais recente\" significam data_lancamento. Quando omitido, usa ordenacao padrao da entidade."
    • addedInput schema / properties / release_scope
      Added value: +{
+  "description": "Escopo de lançamento. released (padrão): somente produtos disponíveis/lançados. upcoming: próximos lançamentos ainda não disponíveis. all: inclui Produzindo, Agendado, Rascunho, Takedown e Lançado.",
+  "enum": [
+    "released",
+    "upcoming",
+    "all"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / released_only
      Added value: +{
+  "description": "Compatibilidade: true equivale a release_scope=released; false equivale a release_scope=all. Prefira release_scope.",
+  "type": "boolean"
+}
  3. First observed

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses the default filtering behavior (only released items) and the effect of release_scope=all, which is valuable. However, it does not mention pagination behavior, response profile defaults, or sensitive data handling, which are relevant for a list tool with many parameters.

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

Conciseness5/5

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

The description is concise, with three sentences that front-load the main purpose, then provide usage context and a critical default behavior. Every sentence earns its place, with no redundant or vague wording.

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

Completeness4/5

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

Given the tool's complexity (10 parameters, output schema present, no nested objects), the description provides sufficient context for correct invocation: it explains the core use case, tenant scope, and the most important parameter (release_scope). While it does not mention response profiles or sensitive data, the schema covers those details, so the description is adequately complete for selection and basic invocation.

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 description coverage is 70%, so the baseline is 3. The description adds meaning to key parameters by explaining that 'lançamento' refers to data_lancamento and clarifying the default behavior of release_scope. This goes beyond the schema's own descriptions and helps the agent understand the primary filtering semantics.

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 uses a specific verb ('Lista') and resource ('registros de produto fonográfico') with a clear scope ('tenant atual'). It distinguishes itself from siblings by specifying the domain (álbuns, singles, EPs) and usage context, making it distinct from other list tools and the corresponding get_produto_fonografico tool.

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

Usage Guidelines4/5

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

The description explicitly states when to use the tool ('Use esta tool para álbuns, singles, EPs e pedidos sobre lançamento musical mais recente') and provides guidance on the default release_scope behavior. It does not explicitly mention when not to use it or name alternative tools as exclusions, but the intended context is clear.

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

All Music360 MCP 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