Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Deezer artist concerts

deezer_artist_events_list
Read-onlyIdempotent

Fetches upcoming Deezer artist concerts and festivals by artistId, returning a paginated event list you can sort by date or distance from a location.

Instructions

List upcoming Deezer artist concerts and festivals. Requires artistId. Returns a list (use cursor when paginated).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "artistId": "<artistId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "deezer_artist_events_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nearNoSort by distance from this point, `latitude,longitude`. Default: soonest first. With `near`, `type` is applied to each page after Deezer sorts by distance, so a page can hold fewer than `limit` events.
typeNoOnly this kind of event. Default: both.
limitNoItems per page, 1 to 100. Default: 50.
cursorNoPass `page.nextCursor` from the previous response to get the next page. Keep the other parameters the same.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
artistIdYesRequired. Deezer artist id, for example `119`.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive, so the safety profile is covered. The description adds the useful constraint that results are limited to upcoming events and pagination via cursor, but says nothing about return shape or ordering defaults (the schema carries the `near` sort nuance, not the description).

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?

Three short sentences, front-loaded with the purpose and the required parameter. "Requires `artistId`" slightly duplicates the schema's required list but is harmless and keeps the definition scannable.

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

Completeness3/5

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

For an 8-parameter, no-output-schema listing tool, the definition covers the essentials but omits anything about result contents or ordering behavior. It is adequate to invoke correctly but not rich enough to set expectations about what comes back.

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 description coverage is 100%, so every parameter including `near`, `type`, `limit`, and `cursor` is already documented in the schema. The description only restates that `artistId` is required and that `cursor` paginates, adding no meaning beyond the structured fields; baseline 3 applies.

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 ("List upcoming Deezer artist concerts and festivals"), which is clearly distinct from artist-metadata siblings like deezer_artist_albums_list. It does not explicitly contrast with deezer_events_list, the closest alternative, so the artist-scoped vs global distinction is only implied by the word "artist".

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

Usage Guidelines3/5

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

"Requires `artistId`" and "use cursor when paginated" give minimal operational guidance, but there is no statement of when to prefer this over deezer_events_list or the other artist sub-resource listers. Usage context is inferred rather than declared.

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

Deploy Server

Other Tools