Skip to main content
Glama

getOrganizationNetworks

List networks a user has privileges on in a Meraki organization, with optional filters for tags, product types, and config templates.

Instructions

List the networks that the user has privileges on in an organization

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoAn optional parameter to filter networks by tags. The filtering is case-sensitive. If tags are included, 'tagsFilterType' should also be included (see below).
perPageNoThe number of entries per page returned. Acceptable range is 3 - 100000. Default is 1000.
endingBeforeNoA token used by the server to indicate the end of the page. Often this is a timestamp or an ID but it is not limited to those. This parameter should not be defined by client applications. The link for the first, last, prev, or next page in the HTTP Link header should define it.
productTypesNoAn optional parameter to filter networks by product type. Results will have at least one of the included product types.
startingAfterNoA token used by the server to indicate the start of the page. Often this is a timestamp or an ID but it is not limited to those. This parameter should not be defined by client applications. The link for the first, last, prev, or next page in the HTTP Link header should define it.
organizationIdYesOrganization ID
tagsFilterTypeNoAn optional parameter of value 'withAnyTags' or 'withAllTags' to indicate whether to return networks which contain ANY or ALL of the included tags. If no type is included, 'withAnyTags' will be selected.
configTemplateIdNoAn optional parameter that is the ID of a config template. Will return all networks bound to that template.
isBoundToConfigTemplateNoAn optional parameter to filter config template bound networks. If configTemplateId is set, this cannot be false.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions that the networks are limited to those the user has privileges on, but it does not disclose pagination behavior, filtering capabilities, or whether this is a read-only operation beyond the verb 'list'. Significant behavioral details are left to the schema.

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?

The description is a single sentence that is front-loaded with the verb and resource. It is concise and free of fluff, though it could be slightly more informative about the tool's scope without becoming verbose.

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

Completeness2/5

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

Despite having an output schema and a fully documented input schema, the high-level description is too bare. It does not mention that the tool supports filtering by tags, product types, or config templates, nor does it hint at pagination. For a tool with 9 parameters, the description fails to set expectations about its capabilities.

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?

Schema description coverage is 100%, so the baseline is 3. The description itself adds no parameter semantics, but the schema thoroughly documents all 9 parameters including filters, pagination tokens, and defaults. The tool description does not need to repeat this.

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?

The description uses a clear verb ('List') and a specific resource ('networks') within an organization, which distinguishes it from sibling tools like getOrganizationDevices or getOrganizations. It unambiguously states what the tool does.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives. The description does not mention any exclusions, prerequisites, or cross-references to sibling tools, leaving the agent to infer usage from the name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dipeshmaindolia001/meraki-mcp-server-testing'

If you have feedback or need assistance with the MCP directory API, please join our Discord server