Skip to main content
Glama
Sign In
Pastebin MCP Server

Pastebin MCP Server

by neopunisher
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Trending Pastes

get_trending_pastes

Fetch the top trending pastes on Pastebin to discover popular public code or text snippets. Provide an optional API key when required.

Instructions

Get the top trending pastes on Pastebin.

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

Input Schema

NameRequiredDescriptionDefault
api_dev_keyNoYour Pastebin Developer API Key.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 behavioral burden, and one sentence does not deliver it. It says nothing about whether the api_dev_key is required for this endpoint, rate limits on the trending feed, result count/pagination, or caching. The only safety context available comes from the name being a 'Get'.

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?

A single front-loaded sentence with zero filler, so nothing needs trimming. It is efficient, though the brevity reflects under-specification rather than a fully earned short form.

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?

An output schema exists, so return values need not be explained, and the single parameter is fully documented in the schema. However, for an unannotated endpoint with an opt-in developer key, the description should at least say whether the call works without authentication or is rate-limited.

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% and there is only one optional parameter (api_dev_key), so the schema already documents it fully. The description adds no meaning about why or when to supply the key, matching the baseline of 3.

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?

States a specific verb+resource ('Get ... pastes') and scopes it to 'trending ... on Pastebin', which implicitly separates it from list_user_pastes (user-scoped) and create_paste/delete_paste (mutations). It does not name any sibling explicitly, so it stops short of a 5.

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?

The word 'trending' implies the use case (fetch the public trending feed rather than a user's pastes), but there is no explicit when-to-use, when-not-to-use, or named alternative. Guidance is only implied.

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