Skip to main content
Glama

Blogs bei trusted blogs suchen

blogs_suchen
Read-only

Sucht im Katalog von trusted blogs nach Blogs für Kooperationen (Sponsored Posts, Linkaufbau). Filter nach Suchbegriff, Themen, Sprache und SEO-Werten. Liefert je Blog Themen, SEO-Werte und einen Link zum Profil. Preise sind nicht enthalten.

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

Input Schema

NameRequiredDescriptionDefault
seiteNo
anzahlNo
themenNoThemen-Slugs aus themen_auflisten, zum Beispiel reisen-outdoor oder essen-kochen. Ein Blog passt, wenn er mindestens eines trägt.
spracheNoSprache aus themen_auflisten
sortierungNoStandard: article_hits mit Suchbegriff, sonst organic_traffic
suchbegriffNoFreitext, durchsucht Blognamen, Beschreibungen und Artikel. Bei mehreren Wörtern müssen alle vorkommen, Füllwörter zählen nicht. Wenige, präzise Wörter finden mehr. 2 bis 200 Zeichen.
nur_dofollowNoNur Blogs, die Do-Follow-Links anbieten
min_domain_rankNo
min_referring_domainsNo

Output Schema

NameRequiredDescriptionDefault
blogsYes
seiteYes
hinweisYes
katalog_linkYesKatalog von trusted blogs mit denselben Filtern; den Suchbegriff übernimmt er nur bei einem einzelnen Wort
seiten_gesamtYesAbrufbare Seiten, höchstens 5
treffer_gesamtYes
registrierung_linkYesKostenlose Registrierung als Unternehmen

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / $defs / BlogTreffer / properties / hauptthema
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Thema, über das der Blog am meisten schreibt, eines der themen. Bei Themenfilter stehen Blogs mit passendem Hauptthema vorn.",
      +  "title": "Hauptthema"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint/openWorldHint annotations already establish this as a safe, closed-catalog read. The description adds useful contract detail (returns topics, SEO values, profile link; no prices), but says nothing about pagination caps, sort defaults, or result limits that affect how the tool behaves.

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?

Four short sentences ordered purpose → filters → outputs → caveat, with the purpose front-loaded. Every sentence carries information; nothing is padded or repetitive.

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 nine-parameter search tool with annotations and an output schema, the description covers intent, filter dimensions, return content, and a pricing caveat. The remaining gap is that it never points to themen_auflisten for valid topic/language slugs, which the schema does reference.

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 description labels the filter families (Suchbegriff, Themen, Sprache, SEO-Werte), which maps to several of the nine parameters and reinforces the schema's own descriptions. With only 56% schema description coverage, it leaves seite, anzahl, sortierung, and the two SEO thresholds unexplained, so it does not fully compensate.

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 names a concrete verb ('Sucht') and resource ('Blogs im Katalog von trusted blogs') and scopes it to a use case (Kooperationen, Sponsored Posts, Linkaufbau). It does not explicitly distinguish itself from the only sibling, themen_auflisten, although that sibling is a helper for slugs rather than a competing search.

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 cooperation/link-building framing gives an agent clear context for when to reach for this tool, and 'Preise sind nicht enthalten' implicitly tells it not to use this for pricing. It stops short of naming alternatives or stating exclusions explicitly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources