Skip to main content
Glama
Sign In
PubNub MCP Server

PubNub MCP Server

by pubnub
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get PubNub General Migration Guide

get_general_migration_guide

Retrieve migration guides for cross-cutting PubNub platform changes, including encryption upgrades, push notification updates, API version migrations, and replacement of deprecated features.

Instructions

Retrieve general migration guides for cross-cutting PubNub platform changes.

  **When to use:**
  - Migrating to a new encryption standard (e.g. 256-bit encryption)
  - Upgrading push notification setup (e.g. APNs HTTP/2, FCM v1)
  - Migrating to new API versions (e.g. Access Manager v3, Objects v2)
  - Replacing deprecated features (e.g. legacy webhooks)

  **Do NOT use for:**
  - SDK version upgrades (e.g. JavaScript v7→v8) → use "get_sdk_migration_guide"
  - General SDK documentation → use "get_sdk_documentation"

  Returns the migration guide content for the specified slug.

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": {
      "slug": "<slug>"
    },
    "name": "get_general_migration_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.4

TDQS

A4.4/5.0
Behavior3/5

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

No annotations provided. Description does not disclose behavioral details beyond stating it returns content. Lacks info on read-only nature, authentication, or response format.

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?

Well-structured with sections, concise, no superfluous information. Every sentence is earned.

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?

Complete enough for a simple 1-parameter tool. Could mention response format, but the examples and scope are sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% coverage, but description provides concrete enum examples in 'When to use' section, adding practical value beyond the schema's enum list.

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?

Clearly states it retrieves general migration guides for cross-cutting PubNub platform changes, specifying verb+resource. Distinguishes from sibling tools get_sdk_migration_guide and get_sdk_documentation.

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

Usage Guidelines5/5

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

Explicitly lists when to use and when NOT to use, with concrete examples and alternative tools named (e.g., 'use get_sdk_migration_guide').

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