Skip to main content
Glama
V2-Digital

V2.ai Insights Scraper MCP

by V2-Digital

search_blogs

Search blog posts by querying titles, content, and authors to find relevant articles from V2.ai Insights.

Instructions

Search blog posts across all content using text query. Searches titles, content, authors, and other fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
limitNo

Implementation Reference

  • The underlying logic for searching blogs, which connects to the Contentful API.
    def _search_blogs(query: str, limit: int = 10):
        """Search blog posts across all content using Contentful's search API"""
        if not os.getenv("CONTENTFUL_SPACE_ID") or not os.getenv("CONTENTFUL_ACCESS_TOKEN"):
            return {
                "error": "Contentful not configured. Set CONTENTFUL_SPACE_ID and CONTENTFUL_ACCESS_TOKEN environment variables."
            }
    
        try:
            from .contentful_client import ContentfulClient
    
            client = ContentfulClient()
            return client.search_blog_posts(
                query=query,
                content_type=os.getenv("CONTENTFUL_CONTENT_TYPE", "blogPost"),
                limit=limit,
            )
        except Exception as e:
            return {"error": f"Error searching Contentful: {str(e)}"}
  • The MCP tool registration for the search_blogs tool.
    @mcp.tool()
    def search_blogs(query: str, limit: int = 10):
        """Search blog posts across all content using text query. Searches titles, content, authors, and other fields."""
        return _search_blogs(query, limit)
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 states the tool searches across multiple fields but does not disclose critical traits like whether it's read-only, how results are ordered, if there's pagination, rate limits, or error handling. For a search tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 appropriately sized with two concise sentences that directly address the tool's function. It is front-loaded with the core purpose and avoids unnecessary details. However, it could be slightly more structured by explicitly separating scope from field details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (search functionality with 2 parameters), lack of annotations, and no output schema, the description is incomplete. It does not explain what the tool returns (e.g., list of posts, metadata), how results are formatted, or any limitations. This leaves the agent with insufficient context to use the tool effectively.

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 adds minimal meaning beyond the input schema. It implies the 'query' parameter searches text across fields like titles and content, but with 0% schema description coverage, the schema provides no details on parameter semantics. The description does not explain the 'limit' parameter or provide syntax examples, so it only partially compensates for the coverage gap.

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 clearly states the tool's purpose: 'Search blog posts across all content using text query' specifies the verb (search), resource (blog posts), and scope (across all content). It distinguishes from siblings like 'get_contentful_posts' or 'get_latest_posts' by emphasizing search functionality rather than retrieval by specific criteria.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It mentions searching 'titles, content, authors, and other fields' but does not specify when this is preferable over siblings like 'get_latest_posts' for recent content or 'summarize_post' for summaries. No exclusions or prerequisites are stated.

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

Install Server

Other Tools

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/V2-Digital/v2-ai-mcp'

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