Skip to main content
Glama
YangLiangwei

PersonalizationMCP

by YangLiangwei

setup_reddit_oauth

Set up Reddit OAuth2 authentication using your client ID and secret to grant authorization for accessing personal Reddit data.

Instructions

    Setup Reddit OAuth2 authentication (initial authentication).
    
    Args:
        client_id: Reddit Client ID
        client_secret: Reddit Client Secret
        redirect_uri: Optional redirect URI (defaults to environment variable or http://localhost:8888/callback)
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_idYes
redirect_uriNo
client_secretYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether the tool returns an authorization URL, stores credentials, requires user interaction, or makes lasting changes; 'Setup' mostly restates the function name.

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?

The description is brief and front-loads the purpose before the Args section. It is compact and easy to scan, though 'authentication' is repeated and the Args block is conventional.

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?

For an OAuth setup tool, the description lacks lifecycle context: how the result should be used and whether complete_reddit_oauth should be called next are not mentioned. The presence of an output schema covers return shape, but the overall flow remains under-specified.

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 description coverage is 0%, but the description compensates by giving each parameter a meaningful label: client_id, client_secret, and redirect_uri with its default behavior. This adds real value beyond the schema's bare property titles and lists.

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 states the action and target clearly: 'Setup Reddit OAuth2 authentication'. Adding '(initial authentication)' helps distinguish it from the completion/refresh Reddit OAuth flow, though it does not explicitly name the sibling tools.

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?

'Initial authentication' implies this is the first step in an OAuth flowabbruch and that it is not for completing or refreshing tokens.skip Alternatives like complete_reddit_oauth and refresh_reddit_token are not mentioned, so the guidance is only implicit rather than explicit.

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