Skip to main content
Glama

get_browser

Identify the active browser for cookie-based authentication to enable video playback control on YouTube and TikTok through the social-video-mcp server.

Instructions

Check which browser is currently being used for cookie-based authentication.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'get_browser' tool, which returns the currently configured browser name and the list of supported browsers.
    server.tool(
      'get_browser',
      'Check which browser is currently being used for cookie-based authentication.',
      {},
      async () => {
        return textResult({ browser: getBrowser(), supported: [...SUPPORTED_BROWSERS] });
      }
    );
  • The helper function 'getBrowser' that retrieves the currently set browser name from the module state.
    export function getBrowser(): BrowserName { return currentBrowser; }
Behavior3/5

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

With no annotations provided, the description carries the full burden. It adds valuable context about cookie-based authentication but fails to describe the return format, possible values, or whether the check operation has any side effects.

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?

Single sentence with no waste. Information is front-loaded with the action verb and key resource immediately stated.

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?

Given no output schema exists, the description should indicate the return value format (string identifier, object, etc.). It mentions checking the browser but doesn't specify what information is returned, leaving a gap for a tool with otherwise low complexity.

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?

Input schema has zero parameters, establishing a baseline of 4. The description correctly implies no arguments are needed to perform the check.

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 uses specific verb 'Check' and identifies the resource 'browser' used for 'cookie-based authentication.' It clearly distinguishes from video playback siblings, though it doesn't explicitly differentiate from set_browser.

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 provided on when to use this tool versus alternatives, or its relationship to set_browser. No prerequisites or conditions mentioned.

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/ronantakizawa/social-video-mcp'

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