Skip to main content
Glama

graph_search_sites

Search SharePoint sites by keyword to locate relevant sites; accepts a required query and an optional result limit up to 50.

Instructions

Search SharePoint sites by keyword.

Needs the Sites.Read.All permission, which requires admin consent. Listing every site without a search term is application-only, so a query is always sent.

Args: query: Search query string. top: Maximum number of results (default 25, maximum 50).

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": {
      "query": "<query>"
    },
    "name": "graph_search_sites"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.10.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It usefully discloses an auth prerequisite (Sites.Read.All, admin consent) and the non-obvious behavioral fact that a query must always be sent because unfiltered listing is application-only. It discloses nothing about the result shape, result ordering, or pagination behavior for a list-style search.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the one-line purpose, followed by the permission and query-always-sent constraints, then a compact Args block. Every sentence adds information an agent needs; nothing is repeated from the schema or restated from the tool name.

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

Completeness3/5

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

For a two-parameter read search with no output schema and no annotations, the definition covers purpose, permission requirement, and both parameters. It leaves the return payload (site fields, ordering, whether top is page size or hard limit) unexplained, which is a meaningful gap for a search tool where the agent must interpret results.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must supply the meaning of both parameters, and it does: query is the search string and top is the result cap with default 25 and maximum 50 — none of which appears in the schema. Note the stated maximum of 50 conflicts with the schema's maximum of 9007199254740991, so the added semantics are valuable but internally inconsistent with the structured field.

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

Purpose4/5

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

States a specific verb and resource: 'Search SharePoint sites by keyword.' The resource noun ('sites') is what separates it from resource-specific siblings such as graph_search_files, graph_search_users or graph_search_people, so an agent can route on it. It does not explicitly address how it differs from the broader-sounding graph_search_all, which keeps it from a 5.

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

Usage Guidelines3/5

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

Usage is implied by the resource (find sites) and a hard precondition is stated (Sites.Read.All + admin consent), which is genuinely useful for deciding whether the call can succeed at all. However, there is no explicit when-to-use/when-not guidance and no named alternative for broader or cross-resource searches. The agent must infer from the resource name alone.

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

Deploy Server

Other Tools