Skip to main content
Glama

toggle_favorite

Toggle the authenticated user's favorite (follow) on a creator, creation, place, or event, or follow an event list (event_zone) / the new-arrivals creation list (creation_zone). Requires a Bearer token (User API token).

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": {
      "target_type": "<target_type>",
      "token": "<token>"
    },
    "name": "toggle_favorite"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYesPublic token of the creator/creation/place. For events, pass the numeric event ID as a string. For event_zone, pass the slug "<kind>/<area>": kind is "all", an event kind, or "period_event"; area is "all" (nationwide) or a region slug (e.g. "kanto"). Following area "all" already covers every region. For creation_zone, pass "all/all".
localeNoResponse language for translatable text fields (names, titles, descriptions). Pass the language the user is conversing in when it is one of the supported locales. Fields without a translation fall back to their source language. Default: ja.
target_typeYesType of the favoritable record. event_zone is an event list (/events/<kind>/<area>); creation_zone is the new-arrivals list (/creations).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / target_type / description
      Previous value: -"Type of the favoritable record."New value: +"Type of the favoritable record. event_zone is an event list (/events/<kind>/<area>); creation_zone is the new-arrivals list (/creations)."
    • changedInput schema / properties / target_type / enum
      Previous value: -[
      -  "creator",
      -  "creation",
      -  "place",
      -  "event"
      -]New value: +[
      +  "creator",
      +  "creation",
      +  "place",
      +  "event",
      +  "event_zone",
      +  "creation_zone"
      +]
    • changedInput schema / properties / token / description
      Previous value: -"Public token of the creator/creation/place. For events, pass the numeric event ID as a string."New value: +"Public token of the creator/creation/place. For events, pass the numeric event ID as a string. For event_zone, pass the slug \"<kind>/<area>\": kind is \"all\", an event kind, or \"period_event\"; area is \"all\" (nationwide) or a region slug (e.g. \"kanto\"). Following area \"all\" already covers every region. For creation_zone, pass \"all/all\"."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this as a non-read-only, non-idempotent, non-destructive write, and the description adds genuinely new behavioral context: the auth requirement (User API Bearer token) and the fact that the same tool also covers list-level following (event_zone/creation_zone) rather than only single records. It stops short of describing the returned state (whether the entity is now favorited or unfavorited), which is the main remaining behavioral gap.

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?

One sentence, front-loaded with the verb and the full target list, followed by the auth requirement. The parenthetical slug examples for event_zone and creation_zone are slightly dense but they carry necessary disambiguation rather than padding.

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?

With no output schema and no annotations about return values, an agent still cannot tell what a successful toggle returns (the resulting favorite state) or what error surfaces on an invalid zone slug. Auth is covered and parameters are fully schematized, so the definition is adequate but not complete for a state-flipping mutation.

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% and the token parameter already documents the per-target-type formats (event ID, kind/area slug, all/all). The description only restates the target taxonomy already present in the target_type enum, adding no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

The description leads with a concrete verb 'Toggle' plus the resource 'favorite (follow)' and enumerates every eligible target (creator, creation, place, event, event_zone, creation_zone). This is clearly separable from the sibling read tools (get_creator, list_events, search) and from rsvp_event, which is a different kind of participation action.

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 implied by the target enumeration and the Bearer-token requirement, so an agent knows the operation is user-scoped and write-oriented. However, it never states when to prefer this over a sibling (e.g. rsvp_event for events) or what happens on a second call beyond the word 'toggle', leaving the when-not to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources