Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Deezer event

deezer_event_get
Read-onlyIdempotent

Retrieves a single upcoming Deezer concert or festival using its event ID, returning venue and artist details for event research and planning.

Instructions

Get one upcoming Deezer concert or festival with venue and artists. Requires eventId.

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": {
      "eventId": "<eventId>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "deezer_event_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
eventIdYesRequired. Deezer event id, for example `13515852`. An event id stops resolving after its date, so take a current id from the events list.
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 readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that results are limited to upcoming events and include nested venue/artist data, but it omits the important caveat (carried only in the schema) that an event id stops resolving after its date.

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 tight sentences with the resource and required input front-loaded and no filler. Every clause carries information.

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 single-record lookup with no output schema, the description tells the agent what comes back (concert/festival with venue and artists) and what input is mandatory. It is nearly complete; the expiry behaviour of ids and the relationship to the list tool would close the remaining gap.

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 `eventId`, `context`, `llm_model` and `conversation_id` are all documented with examples and constraints. The description's 'Requires `eventId`' merely restates the schema's required field and adds no new meaning.

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 ('Get one upcoming Deezer concert or festival') plus the payload contents (venue and artists), which distinguishes it from the plural events-list sibling by singularity and depth. It stops short of naming an alternative explicitly, but the intent is unambiguous.

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

Usage Guidelines2/5

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

Only says 'Requires `eventId`', which is a prerequisite rather than usage guidance. There is no statement of when to prefer this over `deezer_events_list` or how to obtain a valid id; that routing hint lives only in the schema property description, not the tool description.

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