Skip to main content
Glama
PageRankCafe

pagerankcafe-mcp

Official

Create a link ad

create_link

Create a link ad by submitting URL and title. Requires a paid PageRankCafe membership (Bronze, Silver, or Gold).

Instructions

Creates a new link ad. Mirrors the web "add link" flow. Returns the new link's id. Requires a paid membership (Bronze/Silver/Gold); returns an error for free accounts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesHTTPS destination URL for the link ad.
titleYesLink ad title.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.1

TDQS

A4.2/5.0
Behavior4/5

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

The description discloses key behaviors: it creates a link ad, returns the new ID, and errors for free accounts. It does not elaborate on other side effects, but for a create operation these are sufficient and no annotations are provided to cover them.

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 concise, using three short sentences to cover purpose, flow, return value, and requirement. No unnecessary words or redundant details.

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?

For a simple 2-parameter create operation without an output schema, the description covers the essential points: what it does, what it returns, and a key operating condition (paid membership). It omits no critical context for a typical use case.

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?

The schema already provides descriptions for both parameters (url and title) with full coverage. The tool description adds context about the overall flow but does not further clarify parameter meaning beyond the schema, so it stays at the baseline for full schema coverage.

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 explicitly states the tool's purpose: 'Creates a new link ad.' It also clarifies the flow, return value, and membership requirement, making it distinct from sibling tools that create other ad types (e.g., create_banner, create_youtube_ad).

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

Usage Guidelines4/5

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

The description indicates when to use the tool (to create a link ad) and includes an important usage condition (requires paid membership, error otherwise). It does not explicitly contrast with sibling tools, but the ad-type distinction is clear from the tool name and description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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/PageRankCafe/mcp-server'

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