Skip to main content
Glama

Content Pipeline Agent by Nova (CIVAI)

Server Details

I run the Content Pipeline for your Nova products, scan trends, expand seeds into opportunities, ge…

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

B3.4/5.0

Scored across 11 tools

Disambiguation5/5

Each tool maps to a distinct pipeline stage or resource: seeds, opportunities, drafts, jobs, publishing, and indexing are clearly separated. The only close pair, get_job_status vs list_jobs, is still distinguishable as specific-job lookup versus recent-job listing.

Naming Consistency5/5

All tool names use snake_case with a verb-first pattern such as list_seeds, expand_seeds, generate_content, publish_content, and index_content. The convention is consistent throughout, including get_job_status and trigger_scan.

Tool Count5/5

The 11 tools are well-scoped for a content pipeline covering scan, expand, generate, publish, index, and status monitoring. Each tool appears to earn its place without excessive granularity.

Completeness4/5

The core pipeline lifecycle is covered from seed scanning through publishing and indexing, with listing and job status support. Minor gaps exist around editing or inspecting individual draft content and cleaning up drafts, but agents can likely work around them via list_drafts and regeneration.

Available Tools

11 tools
delete_opportunitiesCInspect

Delete staged opportunities that shouldn't be generated.

Inputs: product_id (required), opportunity_ids (required).

expand_seedsCInspect

Expand selected seeds into content opportunities (level 2 of the pipeline).

Inputs: product_id (required), seed_ids, country_code, limit_per_seed, +1 more.

generate_contentBInspect

Generate draft articles for selected opportunities (seo_intent or reward_intent, per the product's pipeline_type).

Inputs: product_id (required), opportunity_ids (required).

get_job_statusBInspect

Check the status/result of a background pipeline job (scan, expand, generate, publish, index all run as jobs).

Inputs: job_id (required).

index_contentCInspect

Submit published URLs to Google Search Console for indexing.

Inputs: urls (required), product_id (required).

list_draftsAInspect

List staged article drafts for a product (unpublished by default).

Inputs: product_id (required), published.

list_jobsCInspect

List recent pipeline jobs.

Inputs: limit, status.

list_opportunitiesCInspect

List staged content opportunities for a product.

Inputs: product_id (required), status.

list_seedsBInspect

List the most recently scanned seeds for a product.

Inputs: product_id (required).

publish_contentCInspect

Publish drafts to the product's configured publish destination(s) (webhook and/or a connected X account).

Inputs: product_id (required), auto_index, article_ids, public_urls.

trigger_scanCInspect

Scan trends for a product and stage candidate seeds (level 1 of the pipeline).

Inputs: product_id (required), limit, country_code, lookback_hours.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      SEO articles that sound like your brand — not generic AI output. TopicForge runs a four-stage pipeline — outline, draft, voice, and CTA — to turn topics into publish-ready articles with FAQ schema, meta, and editorial guardrails.
      7
      53 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to create, schedule, and analyze LinkedIn and X content, manage ideas, media, and a creator knowledge vault, and run approval-gated outreach campaigns through a hosted MCP endpoint.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources