Skip to main content
Glama

Seo Backlinks

by io.github.pipeworx-io

Remember

remember
Idempotent

Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesMemory key (e.g., "subject_property", "target_ticker", "user_preference")
valueYesValue to store (any text — findings, addresses, preferences, notes)

TDQS

A4.7/5.0
Behavior4/5

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

Annotations indicate idempotentHint=true and destructiveHint=false; description adds scoping by identifier, persistent memory for authenticated users, and 24-hour retention for anonymous sessions—behavioral context beyond annotations.

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?

Concise, well-structured description with front-loaded main action, no wasted words, and logical flow from purpose to usage to persistence details.

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?

Complete for a memory storage tool with no output schema: covers purpose, usage timing, storage format, scoping, persistence, and pairing with sibling tools.

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 covers 100% of parameters with descriptions; description adds practical naming conventions (e.g., 'subject_property', 'target_ticker') and clarifies value as 'any text' including findings and preferences.

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?

Description states specific verb 'save' and resource 'data' for reuse, clearly distinguishing from sibling tools 'recall' and 'forget' by mentioning pairing.

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?

Explicitly tells when to use (discover something worth carrying forward), provides storage format (key-value pair scoped by identifier), and contrasts with 'recall' and 'forget' for retrieval/deletion. Also notes authentication-based persistence differences.

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

All Seo Backlinks toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

ask_pipeworx_beta explicitly states it currently behaves identically to ask_pipeworx, making them practically indistinguishable, and ask_pipeworx_grounded is the same router with one extra verification step. The five polymarket_* tools also share overlapping 'find/validate edge' territory, and scan_competitor_ai_presence is a direct wrapper over ai_visibility_check, so an agent must read carefully to pick correctly.

Naming Consistency3/5

Prefix families (ask_pipeworx_*, polymarket_*, seo_backlinks_*, pipeworx_*) provide some predictability, and several tools follow verb_noun (compare_entities, resolve_entity, validate_claim). However, conventions mix single verbs (remember, forget, recall), noun phrases (entity_profile, recent_changes), and seo_referring_domains breaks the seo_backlinks_* family pattern, so the overall scheme is readable but inconsistent.

Tool Count2/5

36 tools is over the 25+ 'too many' threshold even for a broad platform, and the mismatch is far worse given the server is named 'Seo Backlinks' — only 5 of 36 tools actually serve that purpose. The other 31 tools (Pipeworx research, Polymarket betting, memory, subscriptions) belong to a different scope entirely, making the set feel bloated and mislabeled.

Completeness3/5

The five genuine backlink tools cover a single-domain audit well (summary, list, anchors, referring domains, history), but they lack standard SEO workflows like multi-domain or competitor backlink comparison, and there is no tool connecting backlink data to the AI-visibility audit tools. The surrounding Pipeworx surface is extensive, but it belongs to a different domain than the server's stated purpose.

Resources