Skip to main content
Glama
@jam-jam/convert-mcp

@jam-jam/convert-mcp

by titouannwtt

List my AI music analyses of the last 90 days

jj_ai_music_history

Lists your own AI-music analyses from the last 90 days, newest first, 30 per page, with source label, dates, state and report. Use the returned nextBefore cursor to page through results.

Instructions

Lists the caller's own analyses of the last 90 days, newest first, 30 per page (GET /ai-music/history): source label (file name or link), dates, state and report, never any audio. Needs an account and the queue:read scope. Pass the returned "nextBefore" as "before" for the next page. Costs no quota.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jj_ai_music_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
beforeNoCursor: the "nextBefore" value of the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations supplied, the description carries the behavioral burden and does so well: it discloses ordering (newest first), page size (30), returned fields (source label, dates, state, report), the privacy guarantee (never any audio), auth/scope requirements, and that the call costs no quota. This is the kind of context an agent cannot get from structured fields.

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?

One dense, front-loaded sentence that leads with what the tool returns, then auth, pagination, and cost — no filler and no redundancy.

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 simple paged read with no output schema, the description effectively substitutes for one by enumerating the returned fields and the pagination cursor, and it covers auth requirements. Nothing an agent needs in order to call it correctly is missing.

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

Parameters3/5

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

Schema coverage is 100% and the schema already defines "before" as the previous page's "nextBefore", so the description's cursor note largely restates it. It adds the page size and the fact that "nextBefore" is returned, but not enough to exceed the baseline for a fully documented single parameter.

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?

States a precise verb and resource (lists the caller's own analyses), pins the scope (last 90 days, newest first, 30 per page) and even cites the underlying endpoint. That level of specificity cleanly separates it from job-status siblings like jj_ai_music_current or jj_ai_music_get_job.

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?

Gives concrete usage context: requires an account and the queue:read scope, and explains the pagination flow (pass the returned "nextBefore" as "before"). It does not explicitly name a sibling to use instead for a single analysis, but the when-to-use conditions are clear.

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