Skip to main content
Glama
V2-Digital

V2.ai Insights Scraper MCP

by V2-Digital

get_contentful_posts

Fetch blog posts from Contentful CMS to extract content and generate AI-powered summaries for analysis.

Instructions

Fetch posts directly from Contentful CMS (if configured)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Implementation Reference

  • Actual implementation logic for fetching Contentful posts.
    def _get_contentful_posts(limit: int = 10):
        """Fetch posts directly from Contentful (if configured)"""
        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 fetch_contentful_posts
    
            return fetch_contentful_posts(
                content_type=os.getenv("CONTENTFUL_CONTENT_TYPE", "blogPost"), limit=limit
            )
        except Exception as e:
            return {"error": f"Error fetching from Contentful: {str(e)}"}
  • Registration of the 'get_contentful_posts' tool via FastMCP.
    @mcp.tool()
    def get_contentful_posts(limit: int = 10):
        """Fetch posts directly from Contentful CMS (if configured)"""
        return _get_contentful_posts(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 mentions fetching posts and a configuration prerequisite, but does not cover critical aspects such as authentication needs, rate limits, error handling, or what the output looks like (e.g., post format, pagination). This leaves significant gaps for an agent to understand how to invoke it safely and effectively.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded with the main action ('Fetch posts'), though the conditional 'if configured' adds minor complexity. Overall, it is appropriately sized for a simple tool but could be more informative.

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 has no annotations, no output schema, and low parameter coverage, the description is incomplete. It does not explain the return values, error conditions, or behavioral details needed for an agent to use it correctly. The conditional 'if configured' is vague, and without sibling differentiation, the context is insufficient for reliable tool selection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has one parameter ('limit') with 0% description coverage, and the tool description does not mention any parameters or their semantics. This fails to compensate for the lack of schema documentation, leaving the agent without guidance on what 'limit' controls (e.g., number of posts, pagination) or how it interacts with the fetching behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the tool 'fetch[es] posts directly from Contentful CMS', which provides a clear verb ('fetch') and resource ('posts from Contentful CMS'). However, it does not differentiate from sibling tools like 'get_latest_posts' or 'search_blogs', leaving ambiguity about its specific scope or filtering capabilities beyond the basic action.

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 includes a conditional clause 'if configured', which hints at a prerequisite but does not explain what configuration is needed or when to use this tool versus alternatives like 'get_latest_posts' or 'search_blogs'. There is no explicit guidance on when to choose this tool over siblings, making usage unclear.

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