Skip to main content
Glama
sawa-zen

VRChat MCP Server

vrchat_add_favorite

Add VRChat worlds, friends, or avatars to your favorites list with tags for organization using the VRChat MCP Server.

Instructions

Add a new favorite.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYesFavoriteType. Default: friend, Allowed: world | friend | avatar
favoriteIdYesMust be either AvatarID, WorldID or UserID
tagsYesTags indicate which group this favorite belongs to. Adding multiple groups makes it show up in all. Removing it from one in that case removes it from all.

Implementation Reference

  • The handler function that authenticates the VRChat client and calls the favoritesApi.addFavorite method with the provided parameters, returning the result or error as text content.
    async (params) => {
      try {
        await vrchatClient.auth()
        const favorite = await vrchatClient.favoritesApi.addFavorite({
          type: params.type,
          favoriteId: params.favoriteId,
          tags: params.tags,
        })
        return {
          content: [{
            type: 'text',
            text: JSON.stringify(favorite.data, null, 2)
          }]
        }
      } catch (error) {
        return {
          content: [{
            type: 'text',
            text: 'Failed to add favorite: ' + error
          }]
        }
      }
    }
  • Zod input schema validating the tool parameters: type (world, friend, or avatar), favoriteId (string), and tags (non-empty array of strings).
    {
      type: z.enum(['world', 'friend', 'avatar'])
        .describe('FavoriteType. Default: friend, Allowed: world | friend | avatar'),
      favoriteId: z.string().min(1)
        .describe('Must be either AvatarID, WorldID or UserID'),
      tags: z.array(z.string().min(1)).min(1)
        .describe('Tags indicate which group this favorite belongs to. Adding multiple groups makes it show up in all. Removing it from one in that case removes it from all.'),
    },
  • Registers the 'vrchat_add_favorite' tool with the MCP server using server.tool(), providing name, description, input schema, and handler function.
    server.tool(
      'vrchat_add_favorite',
      'Add a new favorite.',
      {
        type: z.enum(['world', 'friend', 'avatar'])
          .describe('FavoriteType. Default: friend, Allowed: world | friend | avatar'),
        favoriteId: z.string().min(1)
          .describe('Must be either AvatarID, WorldID or UserID'),
        tags: z.array(z.string().min(1)).min(1)
          .describe('Tags indicate which group this favorite belongs to. Adding multiple groups makes it show up in all. Removing it from one in that case removes it from all.'),
      },
      async (params) => {
        try {
          await vrchatClient.auth()
          const favorite = await vrchatClient.favoritesApi.addFavorite({
            type: params.type,
            favoriteId: params.favoriteId,
            tags: params.tags,
          })
          return {
            content: [{
              type: 'text',
              text: JSON.stringify(favorite.data, null, 2)
            }]
          }
        } catch (error) {
          return {
            content: [{
              type: 'text',
              text: 'Failed to add favorite: ' + error
            }]
          }
        }
      }
    )
Behavior2/5

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

With no annotations, the description carries full burden but only states it 'adds' without detailing behavioral traits. It doesn't disclose permissions needed, rate limits, whether it's idempotent, or what happens on success/failure, leaving significant gaps for a mutation tool.

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?

The description is a single, efficient sentence with no wasted words, making it front-loaded and easy to parse. It directly conveys the core action without unnecessary elaboration.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, the description is inadequate. It lacks details on behavior, error handling, or return values, failing to provide enough context given the tool's complexity and missing structured data.

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 the schema fully documents parameters. The description adds no extra meaning beyond the schema's details on 'type', 'favoriteId', and 'tags', resulting in a baseline score of 3 as it doesn't compensate but schema does the work.

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 clearly states the action ('Add') and resource ('favorite'), specifying it creates a new favorite. However, it doesn't differentiate from sibling tools like 'vrchat_list_favorites' or 'vrchat_list_favorited_worlds' beyond the basic verb, missing explicit scope comparison.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a valid ID from other tools), exclusions, or comparisons to siblings like 'vrchat_send_friend_request' for friends, leaving usage context implied.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sawa-zen/vrchat-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server