start-content-focus-prompt-analysis
ChatGPTchatgpt block and focusPrompt.chatgptAnalysisStatus update when ready). Requires a focus prompt — set one with set-content-focus-prompt first. Each analysis consumes Analysis credits.By Semji
Semji is a content platform for marketing teams. It helps them plan, score and improve content so it performs both on search engines (SEO) and in AI answers (GEO), while keeping the brand's own voice. This connector gives Claude access to your Semji workspaces so the editorial workflow can be driven in conversation: - Browse workspaces, folders and the content pipeline, with the same filters as the app - Create content drafts in the planning, in bulk from a list of titles, focus keywords and URLs - Set a focus keyword on a content and run its SEO and GEO analysis - Read the resulting Content Score and the typed recommendations per surface: Google Search, Google AI Overview and ChatGPT - Update, assign and organise drafts, and mark a content as published - Launch AI drafting on a content and resolve it, with an explicit confirm step before anything is applied to the draft Access follows the app's own permissions. A user only ever reaches the workspaces their Semji account already has access to, every call is scoped to their organization, and AI drafting is never applied to a draft without an explicit confirm. Semji is used by marketing and SEO teams who own a measurable content pipeline. This connector is aimed at those teams, so they can keep working on that pipeline without leaving Claude.
pageId, threadId, status (pending → processing → completed / failed / stopped) and webUrl (deep link to the agent conversation in Semji). Read a finished run's agent summary with check-agent-run(threadId). Pass the workspaceId and the bulkActionId returned by launch-agent-bulk. Paginated (use pagination.hasMore + page).status is the latest message's state — poll until it is no longer pending/processing, then read output. By default output is trimmed for size: the agent's answer (text) is kept, the model's thinking is dropped, and each tool call is reduced to a compact ledger entry (tool name, its input args, and the result byte size) — the raw fetched content (e.g. page HTML) is omitted. Set full: true to get the complete raw trace (much larger).id (pass it to launch-agent), a type (e.g. CONTENT_LOCALIZER, GEO_EXPERT, EEAT_AUDITOR…), a scope ('PAGE' = runs on a specific page, 'WORKSPACE' = runs at workspace level) and an enabled flag. Use this to discover which agent to launch.anchor (the passage of the draft the thread refers to; null for a document-level comment), its status (open/resolved), and its ordered comments (the first opens the thread, the rest are replies) with author and body. Use this to see what reviewers asked, then act on the draft with update-content and reply with reply-to-comment. Filter with status to focus on open threads.id to get a single search — use this to POLL the async status (status: pending → success/failed; clusterizationStatus is the topic-clustering step). Omit id and pass workspaceId to list the search history (most recent first).id, returns the content metadata (status, assignee, page, last generation) — pass include to fetch the HTML body or the version history. Every content in Semji is wrapped by a page (auto-created shell page if no URL); the returned pageId is what you pass to launch-agent for a PAGE-scoped agent. Without id, requires workspaceId and supports rich filtering (title, page URL, type, status, assignee, folder, score, focus keyword, dates) and sorting. contentScore is the STORED score (0-100), written asynchronously — it can trail the content; read scoreFreshness to know whether it is up_to_date, stale, or frozen (no_focus_keyword/not_started/not_applicable). For a freshly recomputed score use get-content-seo-geo-analysis. In list mode (no id), each content also carries its Google AI Overview presence for the page's focus keyword (aioState: cited/not_cited/no_aio, plus aioCitedUrl) and the date of the last SERP (aioAnalyzedAt).groupBy: channel (organic/paid/direct/social/referral/ai_search/other) and/or subChannel (the traffic SOURCE within a channel — e.g. organic → google/bing, ai_search → chatgpt/perplexity, referral → the referring domain). Typical uses: organic sessions grouped by source → channel='organic' + groupBy=['subChannel']; only Google organic → channel='organic' + subChannel='google'. Source (subChannel) values are dynamic — discover them by grouping on subChannel first. Each row carries sessions/conversions/transactions/revenue/bounceRate/… (+ delta/evolution) and a goals array of the workspace's named custom conversion goals; totals gives the all-rows aggregate (over the full result set, not just the current page). Rows are paginated at 30 per page — check pagination.hasMore and request the next page to get them all (matters when grouping by page or subChannel on large workspaces). Metrics need the Analytics integration. The channel/source breakdown needs the 'channels' entitlement; without it you MUST pass channel='organic' (grouping by channel/subChannel without it returns permission_denied). Dates are YYYY-MM-DD.analytics (sessions/conversions/transactions/revenue/bounceRate/…, returned as { total, byChannel } — an all-channels aggregate plus one row per traffic channel; pass channel to filter to one; each row also carries a goals array of the workspace's named custom conversion goals — name + completions + rate with their delta/evolution. For a per-source breakdown within a channel, e.g. organic by search engine, use find-page-analytics-breakdown), search (clicks/impressions/ctr — pass searchType web/discover), positions (focus-keyword avg position + top3/10/30 distribution), or contents (publications count + avg content score). Each family returns an explicit, documented field set, with *Delta/*Evolution period-over-period variants. Requires periodAfter/periodBefore (YYYY-MM-DD). Metrics are compared to the immediately-preceding period of equal length by default (returned as previousMetrics); pass comparePeriod* to compare against a specific period instead. Metrics need the workspace to have the matching integration (Search Console / Analytics) and the Performance entitlement — otherwise they come back null. Accepts the same page filters as find-pages. Each page row also carries its Google AI Overview presence (aioState: cited/not_cited/no_aio, plus aioCitedUrl) and the date of the last SERP (aioAnalyzedAt).Page.contentScore (may lag a live re-analysis). Each page also carries its Google AI Overview presence for the focus keyword (aioState: cited/not_cited/no_aio, plus aioCitedUrl) and the date of the last SERP (aioAnalyzedAt). For over-a-period performance metrics (clicks/impressions/positions with date ranges and comparison), use find-page-performance.id, returns the workspace metadata; pass include to fetch related collections (workflow statuses, folder tree, team, content counts). Without id, returns a flat list of all accessible workspaces. Each workspace has its own contents, keywords, folders, and team — use the returned workspaceId with find-contents, create-contents, browse-folders, etc.promptId). Returns AI-visibility metrics broken down by one dimension: brands (per tracked competitor, incl. you), platforms (per AI platform — REQUIRES a brand), or topics (per topic × brand grid, paginated). One metric per call — visibility (0.65×mention + 0.35×citation, default), mention, or citation; call again with another metric for the other widgets. evolution: true returns a time series per bucket (brands/platforms only; periodicity day→year, default year) instead of a single snapshot. Rates/scores are 0–100 percentages. Brand/topic/persona/funnelStage filters accept human-readable values listed in availableFilters; unresolvable values return an error listing them. Dates are plain YYYY-MM-DD, default last 90 days. Requires the workspace's GEO benchmark plan (a clean permission error otherwise). Note: this endpoint exposes current-period values only — no per-row deltas.responseId feeds geo-prompt-response to read the full answer. Pass include to fetch a subset of sections and cut cost when iterating — e.g. include:["responses"] while paginating answers; prompt metadata is always returned. metrics: null with a warning means no snapshot in the range (not an error). The citedBrands/mentionedBrands/providers filters apply to both the metrics and the responses sections, like the screen. Dates are plain YYYY-MM-DD; defaults: last 90 days, compared like the Intelligence Hub screen (previous calendar months for a month-aligned range, otherwise the same-length window shifted back). Keep responsesLimit low: each response row is expensive to produce server-side.responses[].responseId ({provider}-{date}). A null answer with a note means the run stored no answer.kpis aggregates the same metrics over ALL matching prompts. Rates and scores are 0–100 percentages; deltas are points vs the comparison period. Brand filters (mentionedBrands/citedBrands — include your own brand to audit your presence) and topic/persona/funnelStage accept human-readable values: valid values are listed in the response's availableFilters, and an unresolvable value returns an error listing them. Dates are plain YYYY-MM-DD; defaults: last 90 days, compared like the Intelligence Hub screen (previous calendar months for a month-aligned range, otherwise the same-length window shifted back). AI platforms not enabled on the workspace plan silently return no data.dimension selects the breakdown: domains (Top domains, by owning brand's root domain — the only paginated dimension), pageTypes (by page type), platforms (by AI platform), sourceScopes (self = your own, configured = a tracked competitor, inferred = an indirect source). Each row is an occurrence count, its percentage share of the period total, the countDelta (absolute change vs the comparison period) and countEvolution (percent change; null when the bucket is new). Filters mirror geo-sources (providers, pageTypes, sourceTypes, sources, topic/persona/funnelStage); valid values are listed in availableFilters and an unresolvable value returns an error listing them. Dates are plain YYYY-MM-DD; defaults: last 90 days, compared like the Intelligence Hub screen (previous calendar months for a month-aligned range, otherwise the same-length window shifted back). AI platforms not enabled on the workspace plan silently return no data.kpis aggregates total sources, distinct domains and your own sources count, with deltas. The sources filter accepts brand names or domains (your own brand included — audit where YOU appear) plus the special value indirect for sources not owned by any configured competitor; valid values are listed in availableFilters.sources and an unresolvable value returns an error listing them. Dates are plain YYYY-MM-DD; defaults: last 90 days, compared like the Intelligence Hub screen (previous calendar months for a month-aligned range, otherwise the same-length window shifted back). AI platforms not enabled on the workspace plan silently return no data.googleSearch (SEO) and googleAiOverview come from the keyword analysis; chatgpt comes from the keyword's focus prompt analysis. Each surface block carries the overall score plus typed recommendations (topics, search intents, questions for SEO; GEO topics, cited sources, mentioned brands and the AI response preview for AI Overview and ChatGPT), and is null until its analysis is ready — check the matching *AnalysisStatus on focusKeyword/focusPrompt. The wrapping page, focus keyword and focus prompt are resolved automatically from the content. These scores are recomputed LIVE against the current draft body and may differ from the STORED contentScore returned by find-contents (which trails — see its scoreFreshness).bulkActionId plus counts: requested (targeted), scheduled (eligible runs created — a content is eligible when its page has a successfully-analysed focus keyword), skipped (requested − scheduled). Track the batch with check-agent-batch(bulkActionId), then read each finished run's summary with check-agent-run(threadId). Consumes AI-writing credits per scheduled run; if credits are insufficient, the agent is out of plan, or AI access is denied, NOTHING is created and the error explains why. For a single content, launch-agent is simpler.status field indicates whether the voice is ready (success) or still being analyzed (pending, error).totalTraffic sums the estimated traffic of ALL matching rows (not just the page). Dynamic filters (competitors, topic, persona, funnelStage) accept human-readable values — valid values are listed in the response's availableFilters, and an unresolvable value returns an error listing them. Keyword-level fields and filters only have data for the report's effective month: omit month to query it; other months (report.availableMonths) carry page-level data only.groupBy axis, carrying nbPages, traffic, and the long-tail / short-tail traffic split. groupBy picks the aggregation: competitor (default, one total row per site), brand (branded/not_branded/branded_for_other_domain), category (page category), position (SERP position bucket), topic / persona / funnel (AI-classified dimensions, resolved to option names), or month / monthlyProduction (12-month series, incompatible with month). Dynamic filters (competitors, topic, persona, funnelStage) accept human-readable values listed in the response's availableFilters; an unresolvable value returns an error listing them. Use month (report.availableMonths) to target a specific analyzed month; omit it for the effective month. For a page-level breakdown (per keyword/URL) use seo-page-data-explorer instead.chatgpt surface of get-content-seo-geo-analysis. Creates the prompt from the given text (or reuses an identical one) and points the focus at it. Requires a focus keyword on the wrapping page — set one with set-content-focus-keyword first. Run start-content-focus-prompt-analysis afterwards to analyse it.chatgpt block and focusPrompt.chatgptAnalysisStatus update when ready). Requires a focus prompt — set one with set-content-focus-prompt first. Each analysis consumes Analysis credits.tracked boolean that reflects whether THIS call actually queued a new generation: tracked=true means the backend created a new generation for this content (poll its status with check-content-generation); tracked=false means the backend did not start a new generation for this content and the entry carries a reason explaining why (no focus keyword / SEO analysis not 'success' / a prior generation is already in flight / a stale terminal generation is attached). When a prior in-flight generation blocked the call, you can still poll check-content-generation on the same contentId to observe its progress. Each target content must be linked to a page with a focus keyword whose SEO analysis is complete. Use type='optimize' to improve existing HTML, type='replace' to regenerate from scratch. Use retry=true to relaunch previously failed generations. Consumes AI Writing credits — the exact cost varies with generation type, fact-checking, and brand voice; check the remaining balance with get-account before bulk runs. Poll each result via check-content-generation.Add this badge to your site or README. It links to this page.
HTML
<a href="https://mcp-app-store.keenethics-labs.com/app/semji"><img src="https://mcp-app-store.keenethics-labs.com/badges/listed-on-mcp-app-store.svg" alt="Listed on MCP App Store" width="220" height="44"></a>
Markdown
[](https://mcp-app-store.keenethics-labs.com/app/semji)