Skip to main content
Glama

Server Details

AI marketing: SEO articles, trend scouting, competitor analysis, social media, lead magnets

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Unhealthy
OAuth
Requires browser extension
Last Tested
Transport
Streamable HTTP
URL
Repository
citedy/citedy-seo-agent
GitHub Stars
18
Server Listing
SEO Content Autopilot by Citedy

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool update
    • Changedshorts.script1 field changed
      • addedInput schema / properties / favorite_id
        Added value: +{
        +  "description": "Optional favorite (product identity) ID from ai_favorites — use this to scope gaps/KB to a specific product. Added in UGC Strike v2 P1-0; fully backward-compatible (absent → same legacy behaviour).",
        +  "format": "uuid",
        +  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
        +  "type": "string"
        +}
  2. 1 tool update
    • Addedshorts.publish
  3. 1 tool update
    • Addedgsc.report
  4. 4 tool updates
    • Addedarticle.delete
    • Changedarticle.generate1 field changed
      • addedInput schema / properties / auto_publish
        Added value: +{
        +  "description": "Publish article immediately after generation. When false, article stays as draft (status=generated). Default uses tenant setting.",
        +  "type": "boolean"
        +}
    • Addedarticle.publish
    • Addedarticle.unpublish
  5. 2 tool updates
    • Changedarticle.generate2 fields changed
      • addedInput schema / properties / wait_for_completion
        Added value: +{
        +  "default": true,
        +  "description": "Wait synchronously for article completion before returning",
        +  "type": "boolean"
        +}
      • changedInput schema / required
        Previous value: -[
        -  "language",
        -  "size",
        -  "mode",
        -  "enable_search",
        -  "illustrations",
        -  "audio",
        -  "disable_competition"
        -]New value: +[
        +  "language",
        +  "size",
        +  "mode",
        +  "enable_search",
        +  "illustrations",
        +  "audio",
        +  "disable_competition",
        +  "wait_for_completion"
        +]
    • Addedarticle.get
  6. 52 tool updates
    • First observedadapt.generate
    • First observedagent.health
    • First observedagent.me
    • First observedagent.status
    • First observedarticle.generate
    • First observedarticle.list
    • First observedbrand.scan
    • First observedbrand.scan.get
    • First observedcompetitors.discover
    • First observedcompetitors.scout
    • First observedgaps.generate
    • First observedgaps.list
    • First observedingest.batch
    • First observedingest.content.get
    • First observedingest.create
    • First observedingest.get
    • First observedleadmagnet.archive
    • First observedleadmagnet.generate
    • First observedleadmagnet.get
    • First observedleadmagnet.publish
    • First observedpersonas.list
    • First observedproducts.create
    • First observedproducts.delete
    • First observedproducts.list
    • First observedproducts.search
    • First observedschedule.gaps
    • First observedschedule.list
    • First observedscout.reddit
    • First observedscout.reddit.result
    • First observedscout.x
    • First observedscout.x.result
    • First observedseo.headings.check
    • First observedseo.internal_links.plan
    • First observedseo.links.analyze
    • First observedseo.meta_tags.check
    • First observedseo.og_image.generate
    • First observedseo.og.preview
    • First observedseo.robots.check
    • First observedseo.schema.validate
    • First observedseo.sitemap.check
    • First observedsession.create
    • First observedsettings.get
    • First observedshorts.avatar
    • First observedshorts.generate
    • First observedshorts.get
    • First observedshorts.merge
    • First observedshorts.script
    • First observedsocial.publish
    • First observedwebhooks.delete
    • First observedwebhooks.deliveries
    • First observedwebhooks.list
    • First observedwebhooks.register

Frequently Asked Questions

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0
Disambiguation2/5

The tool set has significant ambiguity and overlap, particularly in the polling/status-checking tools (e.g., article.get, brand.scan.get, ingest.get, leadmagnet.get, scout.reddit.result, scout.x.result, shorts.get) which all serve similar purposes but are scattered across different domains. Additionally, tools like 'agent.status' and 'agent.health' have overlapping operational checks, and 'seo.meta_tags.check' vs 'seo.og.preview' could be confused for meta analysis. While some tools are distinct, the overall set is cluttered with redundant patterns.

Naming Consistency4/5

Naming is mostly consistent with a clear verb_noun pattern (e.g., article.generate, brand.scan, gaps.list) and uses snake_case throughout. However, there are minor deviations like 'agent.me' (which uses a pronoun instead of a verb) and 'shorts.avatar' (noun_noun instead of verb_noun), and some tools have dot-separated prefixes (e.g., seo.schema.validate) that add slight inconsistency. Overall, the naming is predictable and readable.

Tool Count2/5

With 58 tools, the count is excessive for a single server, indicating poor scoping and likely bloat. Many tools could be consolidated (e.g., polling tools into a generic status check) or split into separate servers for distinct domains like SEO analysis, content generation, and social media. This high number makes the tool surface overwhelming and difficult for agents to navigate efficiently.

Completeness4/5

The tool set covers a broad range of SEO and content marketing operations, including article generation, SEO checks, competitor analysis, social media scouting, and video creation, with good CRUD coverage in areas like articles and webhooks. However, there are minor gaps, such as no direct update tools for articles or settings (only get/delete/publish operations), and some domains like lead magnets lack full lifecycle management (e.g., no update tool). Overall, the surface is largely complete for its intended purpose.