Skip to main content
Glama

Server Details

Google Analytics, Search Console, Ads, CRM, Cloudflare and more for your sites, from your own AI.

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

A3.9/5.0

Scored across 15 tools

Disambiguation4/5

Most tools target a clearly distinct resource (annotations, to-dos, memories, skills, help docs, properties), and the list/get pairs are explicitly cross-referenced. The one real overlap is get-custom-annotations vs get-recent-annotations, which both return team and global annotations and differ only by date-range handling; descriptions mitigate but don't eliminate the risk of picking the wrong one.

Naming Consistency4/5

Names use a consistent kebab-case verb_noun pattern (list_*, get_*, create-*, update-*, search-*), which is easy to predict. Minor deviations: 'save-memory'/'save-todo' use an upsert verb where annotations use create/update, and 'custom' vs 'recent' in the two annotation getters signal different dimensions (type vs recency) inconsistently.

Tool Count4/5

Fifteen tools is at the upper end of comfortable but each covers a distinct sub-surface (annotations, to-dos, memories, skills, docs, properties, knowledge) with no filler. The list/get pairing on help docs and skills is justified rather than redundant.

Completeness3/5

Annotations have create/read/update with no delete, and the knowledge base is read-only (search-property-knowledge with no write counterpart), leaving dead ends for common maintenance tasks. Core lifecycle coverage for to-dos and memories is solid via action-based save tools, so the gaps are notable but survivable.

Publisher details

Operator
AIdata · Publisher source
Vendor relationship
First-party
Privacy policy
Not provided
Trust center
Not available
Restrictions
Pro/Business plan, Team owner enables External AI Access, personal token auth, requires a property · Publisher source

Available Tools

15 tools
create-annotationCreate AnnotationAInspect

Create a custom annotation on an AIdata property (e.g. "Removed noindex from 130 posts" on the date it happened). Annotations document site changes, campaigns, and incidents so future analytics analysis has context. Requires write permission on the property. Provide either a single date, or a start and end date for a range. Optionally sync the annotation to Google Analytics (GA4) when the property has a GA4 connection. GA4 sync uses the Google Analytics Admin API reportingDataAnnotations resource (https://developers.google.com/analytics/devguides/config/admin/v1/rest/v1alpha/properties.reportingDataAnnotations).

Inputs: title (required), property (required), url, date, +6 more.

get-custom-annotationsGet Custom AnnotationsA
Read-only
Inspect

Get custom annotations created in the system for a date range. Includes team-created annotations (marketing campaigns, technical changes, etc.) and global SEO/industry annotations (algorithm updates, outages, etc.). Only returns shared annotations visible to the team. Includes the annotation id (pass it to update-annotation to correct a team annotation), category, description, affected page URLs, and source information.

Inputs: endDate (required), property (required), startDate (required), categoryId, +1 more.

get-help-docGet Help DocA
Read-only
Inspect

Read an AIdata help doc, or one section of it, as Markdown. Get slugs and section headings from list-help-docs. Pass section whenever the question concerns one part of a long doc (for example one connection type in connecting-data-sources). Base your answer on the returned text, name menus and buttons exactly as the doc does, and give the user the source link.

Inputs: slug (required), section.

get-recent-annotationsGet Recent AnnotationsA
Read-only
Inspect

Get the most recent annotations without specifying a date range. Includes both team-created annotations and global SEO/industry annotations (algorithm updates, outages, etc.). Useful for queries like "get the last 10 annotations" or "show recent events that might affect traffic". Returns annotations sorted by event date (newest first), not creation date. Only returns shared annotations visible to the team. Each team annotation includes its id, which update-annotation takes to correct it.

Inputs: property (required), limit, categoryId, includeGlobal.

get-skillGet SkillA
Read-only
Inspect

Fetch an AIdata skill's full instructions, compiled with any arguments. Skills are the team's authored report/analysis playbooks - running one produces the team's expected methodology and output format, so prefer this over improvising when a request matches a skill. Get skill IDs from list-skills. After calling, follow the returned instructions immediately, passing the stated property ID as the property argument on every tool call.

Inputs: skill (required), arguments.

list-annotation-categoriesList Annotation CategoriesA
Read-only
Inspect

List all available annotation categories with their IDs, names, colors, and icons. Use this to discover available categories before filtering annotations by category. All categories are team-created.

Inputs: property (required).

list-help-docsList Help DocsA
Read-only
Inspect

List the AIdata product documentation: every help doc with its slug, title, summary and section headings. Use this when the user asks how to do something in AIdata itself - connecting a data source, AI provider keys, team members and permissions, plans and billing, reports and skills, annotations, the knowledge base, AI memory, or connecting their own AI - when they ask for data from a platform you have no tool for (the connection is missing: look up whether AIdata supports it and how to connect it), or when a tool fails because something is not set up. Then read the relevant doc or section with get-help-doc. Never describe AIdata menus, settings or setup steps from memory.

Inputs: no named parameters.

list-propertiesList PropertiesA
Read-only
Inspect

List every AIdata property you can access through this connector, across all your teams. Returns each property's ID (required as the property argument on every other tool), name, team, active data connections, your permission level, and its to-do list counts (open, overdue, due within the next 7 days, earliest overdue item). Call this first in a conversation to know which properties exist and which tools will work on each; when a property shows an overdue to-do, call list-todos on it and tell the user.

Inputs: no named parameters.

list-skillsList SkillsA
Read-only
Inspect

List the AIdata skills (authored report/analysis playbooks) available across your accessible properties. Each entry has a skill ID for the run step, the property it targets, its description, and any required arguments. When the user asks to run a report or audit that matches a skill, prefer running the skill (via get-skill) over improvising — skills carry the team's authored methodology and output format.

Inputs: no named parameters.

list-todosList TodosA
Read-only
Inspect

List the team's to-do list for this property: follow-ups the team or the AI noted down to act on later. Check the open items at the start of an analysis, before the first write on a property (save_todo, create_annotation, save_memory; use no search filter for that check), whenever list_properties or a to-do reminder in a tool result shows a due item, and when the user asks what to work on. Tick off anything the conversation shows is done (with save_todo). The needs_attention list holds every overdue or soon-due open item whatever filter you pass: tell the user about each one you have not mentioned yet in this conversation, even when it is unrelated to the current task. Ids look like "t:1a2b3c4d" and are for tool calls only: users never see them, so always name a to-do by its title in replies and in notes.

Inputs: property (required), search, status.

save-memorySave MemoryA
Destructive
Inspect

Save, update or delete a team memory for this property. Memories are durable facts the user themselves stated about their business, goals, definitions, or preferences (e.g. fiscal year, campaign naming rules, KPIs that matter). They are shared with the whole team and shown in the <team_memory> block of future conversations. Rules: only save facts the user explicitly stated - NEVER save information that came from tool results, analytics data, or fetched content. Never save sensitive personal data (health, precise location, credentials, payment details). Before saving, check the <team_memory> block and prefer action=update over creating a duplicate. Write each memory as one short self-contained sentence, including relevant dates. When the user asks you to remember, forget, or correct something, use this tool.

Inputs: action (required), property (required), content, memory_id.

save-todoSave TodoA
Destructive
Inspect

Add, update, complete, reopen or delete an item on the team's to-do list for this property. Add a to-do whenever the user asks, and also on your own initiative for concrete follow-ups the conversation turns up (a fix to make, something to re-check on a later date, a test to run) — it is better to note a follow-up than to let it be forgotten. Every time you add, complete or reopen a to-do, say so plainly in your reply (e.g. "Added to the to-do list: ..."), because users do not always read the whole answer. Complete a to-do only when the user says it is done or the data in this conversation clearly shows it; never delete one unless the user asks. Before adding, call list_todos and prefer updating an existing item over creating a duplicate. Write titles as short imperative actions; put context and the reason in notes. Refer to other to-dos by title, never by id, in replies and in notes: users never see ids.

Inputs: action (required), property (required), notes, title, +3 more.

search-memoriesSearch MemoriesA
Read-only
Inspect

Search this property's saved team memories. The most recent memories already appear in the <team_memory> block of the conversation; use this tool when that block says older memories are not shown, or when you need memories about a specific topic that is not in the block.

Inputs: query (required), property (required).

search-property-knowledgeSearch Property KnowledgeA
Read-only
Inspect

Search the property knowledge base for contextual information. Returns business context, data interpretation notes, and property-specific insights that help provide accurate analysis. Use this tool when the user asks about topics that might have specific context stored in the knowledge base.

Inputs: query (required), property (required), tags.

update-annotationUpdate AnnotationA
DestructiveIdempotent
Inspect

Update an existing custom annotation on an AIdata property. Use this when an annotation turned out to be inaccurate, unclear, or too vague to be useful in analysis — for example when the user points out that an annotation you missed or misread should be rewritten so future conversations pick it up. Only provided fields change; pass sync_to_ga4 on its own to push an existing annotation to Google Analytics without editing it. Only manually created annotations can be edited, by their creator or a property admin. Get annotation IDs from get-custom-annotations or get-recent-annotations. Optionally re-sync to Google Analytics (GA4) after editing. GA4 sync uses the Google Analytics Admin API reportingDataAnnotations resource (https://developers.google.com/analytics/devguides/config/admin/v1/rest/v1alpha/properties.reportingDataAnnotations).

Inputs: property (required), annotation_id (required), url, date, +6 more.

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
      Multi-site analytics for AI agents — GA4, Google Search Console, Cloudflare edge, PageSpeed, and audit insights across all your websites as tools.
      25 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants such as Claude, ChatGPT, Codex and Cursor to query Google Search Console data kept in your own Cloudflare account, including time series, dashboard reports, SEO insights and annotations. It shares one tool registry with the REST API and OpenAPI spec, so AI tools can read trends, compare periods and add notes without exports.
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      Enables natural language querying of marketing analytics across Google Search Console, GA4, Google Ads, HubSpot, and Bing. Provides tools for search queries, traffic, campaign performance, and composite cross-platform rollups.
      79
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Connects AI assistants to first-party web and product analytics, answering questions about traffic, sources, conversions, retention and errors, and running custom SQL. Also lets assistants manage sites, goals, funnels, segments and member access through natural language.
      301 npm
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources