Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Deezer events

deezer_events_list
Read-onlyIdempotent

Search upcoming Deezer concerts and festivals by place or act, with optional event-type filters and pagination, to find relevant live events.

Instructions

Search upcoming Deezer concerts and festivals by place or act. Optional inputs: query, type, limit and cursor. 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": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "deezer_events_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOnly this kind of event. Default: both.
limitNoItems per page, 1 to 100. Default: 50.
queryNoA place or an act, for example `London` or `Metallica`. Without it the endpoint lists events Deezer still marks as pending in the United Kingdom.
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.
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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive behavior, so the safety profile is covered. The description adds that results are a list and that pagination is cursor-based, but says nothing about result ordering, coverage, or the empty-query default, which the schema happens to carry instead.

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?

Two sentences, front-loaded with the search scope, then the optional inputs and return/pagination note. No filler and nothing buried.

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?

For a 7-parameter read-only listing tool with full schema coverage and no output schema, the description covers intent, inputs and pagination adequately. It omits the required meta-parameters (context, llm_model, conversation_id handshake), though those are fully described in the schema.

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 the place/act meaning of query and the type enum, is already documented in structured data. The description only restates the optional parameter names and the cursor reuse rule, adding little beyond the schema.

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?

The description gives a specific verb and resource: "Search upcoming Deezer concerts and festivals," plus a scoping axis ("by place or act"). It is clear enough to separate this listing endpoint from get-style siblings, but it never contrasts itself with the other Deezer event-adjacent listings.

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?

It states that query/type/limit/cursor are optional and instructs the agent to reuse the cursor for pagination, which is real usage guidance. Beyond that it does not say when this tool should be preferred over alternatives or what happens when no query is supplied.

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