Skip to main content
Glama
Sign In
Socials MCP

Socials MCP

by Brainrot-Creations
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

socials_get_agent_tab

Retrieve the currently pinned Socials agent tab, including its URL, title, and platform (X, LinkedIn, Reddit, YouTube). If none is set, returns null, indicating you need to open one with socials_open_tab.

Instructions

Get the pinned Socials agent tab (URL, title, platform: x, linkedin, reddit, youtube, or null). Null if none set yet—then call socials_open_tab.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden of explaining behavior. It transparently discloses that the tool returns null when no tab is set and instructs to call socials_open_tab in that case. However, it does not mention any potential errors or side effects, though as a getter these are unlikely.

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, well-structured sentence that front-loads the main action and includes important conditional guidance. Every phrase earns its place with no redundancy.

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

Completeness5/5

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

Given no output schema, the description sufficiently explains the return value (URL, title, platform, null) and the follow-up action. It also provides enough context to distinguish from sibling tools like socials_set_agent_tab and socials_open_tab, making it complete for the tool's simplicity.

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?

The tool has zero parameters, so the baseline is 4. The description adds value by explaining the return values and null semantics, which complements the empty schema. No parameter details are needed.

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 clearly states the verb 'Get' and the specific resource 'pinned Socials agent tab', and enumerates the return fields (URL, title, platform) including possible values. It distinguishes itself from sibling tools like socials_get_active_tab by specifying 'pinned agent tab'.

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?

The description provides explicit guidance on when to use this tool: it should be called to retrieve the pinned agent tab, and if the result is null, the agent should call socials_open_tab. This directly addresses usage context and provides an alternative action.

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