Skip to main content
Glama

vibo_list_notifications

Read-only

Retrieve Vibo notifications—song additions, comments, and DJ updates—with read state and linked event or section IDs to track activity.

Instructions

List your Vibo notifications (song additions, comments, DJ updates, etc.) with read state and linked event/section ids.

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": "vibo_list_notifications"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNoNumber of items to skip, for paging (default 0).
viewNocompact (default) strips image/avatar URLs; "full" returns Vibo's payload untouched; "brief" returns one line per notification: header — <ISO date | no date> — <read|unread>, inside the untrusted-data envelope, with "-- none" for none and "-- N of M shown" / "-- more" when partial.
limitNoMax items to return (default 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.5.0
    • changedInput schema / properties / view / description
      Previous value: -"Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact strips image/avatar URLs from the response; \"full\" returns Vibo's payload untouched. No field projection: this server has no verified record of which Vibo fields matter, and inventing one would risk dropping a field a caller needs."New value: +"compact (default) strips image/avatar URLs; \"full\" returns Vibo's payload untouched; \"brief\" returns one line per notification: header — <ISO date | no date> — <read|unread>, inside the untrusted-data envelope, with \"-- none\" for none and \"-- N of M shown\" / \"-- more\" when partial."
    • changedInput schema / properties / view / enum
      Previous value: -[
      -  "compact",
      -  "full"
      -]New value: +[
      +  "compact",
      +  "full",
      +  "brief"
      +]
  2. Changed1 schema field changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed1 schema field changedv1.8.0
    • addedInput schema / properties / view
      Added value: +{
      +  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact strips image/avatar URLs from the response; \"full\" returns Vibo's payload untouched. No field projection: this server has no verified record of which Vibo fields matter, and inventing one would risk dropping a field a caller needs.",
      +  "enum": [
      +    "compact",
      +    "full"
      +  ],
      +  "type": "string"
      +}
  4. First observedv1.3.1

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description usefully adds that results carry read state and linked event/section ids. It does not mention ordering, defaults, or the compact/full/brief payload variation, all of which live only in the schema.

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?

A single dense sentence with the resource and the returned fields front-loaded and no wasted clauses. It could have spent one more clause routing to the sibling tools, but nothing present is filler.

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?

There is no output schema, so the description's mention of read state and linked event/section ids carries real weight for anticipating the response shape. Paging and view modes are covered by the schema, leaving only ordering and the untrusted-data envelope unaddressed.

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%, with skip, limit, and a three-value view enum fully documented in the schema itself. The description adds no additional meaning about paging behavior or view selection, so the baseline of 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 your Vibo notifications") and enumerates the content types (song additions, comments, DJ updates) plus the payload fields (read state, linked event/section ids). This separates it from the count-only and mark-read siblings implicitly, though it never names them explicitly.

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?

Usage is only implied: the examples of notification kinds suggest checking what happened recently. There is no explicit statement of when to prefer this over vibo_get_notifications_count or when to follow up with vibo_mark_notifications_read, and no prerequisites or exclusions are given.

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