Skip to main content
Glama

Visibility Genies

Read the project summary

get_project_summary
Read-only

Where a project stands, in one call: the Summary page's six answers (site health, Google visits, what AI answers say, how strong your links are, who beats you, what to do this week), each with the newest day its data comes from, and Home's scores and changes with when each was measured. Read it first, before deciding what to buy. A project without data gets the same empty texts the pages show. Free: it reads saved data and the project's own Search Console connection, and buys nothing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>"
    },
    "name": "get_project_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.

Output Schema

NameRequiredDescriptionDefault
metaNo
scoresYes
changesYes
questionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnly/non-destructive/closed-world, and the description adds genuine context beyond them: the call is free, buys nothing, reads saved data plus the project's own Search Console connection, and returns per-metric data freshness plus measurement timestamps. It also discloses the empty-state behavior, which tells the agent how to interpret a null-data response.

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?

Front-loaded with the core value, then short sentences on freshness, empty state, and cost. The opening sentence is dense with parentheticals, but every clause carries information an agent would otherwise have to discover.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not enumerate return fields, and it still covers cost, data sources, freshness semantics, and empty-state handling for a low-complexity single-parameter read.

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

Parameters3/5

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

The single projectId parameter is fully documented in the schema, including its billing linkage and the pointer to list_projects, so the description does not need to restate it. It adds nothing parameter-level, which is acceptable at 100% coverage but not above baseline.

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

Purpose5/5

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

"Where a project stands, in one call" is followed by an explicit enumeration of the six answers returned (site health, Google visits, AI answers, link strength, competitors, weekly actions), which makes the resource unmistakable and hard to confuse with siblings like get_spend_summary or get_project_context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Read it first, before deciding what to buy" gives a clear directive about ordering relative to other calls, which is real usage guidance. It stops short of naming specific alternative tools or exclusion conditions, so it is not a full when/when-not statement.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources