Skip to main content
Glama

getOrganizationDevices

List network-assigned Meraki devices in an organization, with optional filters for network, model, serial, MAC, tags, and product type.

Instructions

List the devices in an organization that have been assigned to a network.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
macNoOptional parameter to filter devices by MAC address. All returned devices will have a MAC address that contains the search term or is an exact match.
macsNoOptional parameter to filter devices by one or more MAC addresses. All returned devices will have a MAC address that is an exact match.
nameNoOptional parameter to filter devices by name. All returned devices will have a name that contains the search term or is an exact match.
tagsNoOptional parameter to filter devices by tags.
modelNoOptional parameter to filter devices by model. All returned devices will have a model that contains the search term or is an exact match.
modelsNoOptional parameter to filter devices by one or more models. All returned devices will have a model that is an exact match.
serialNoOptional parameter to filter devices by serial number. All returned devices will have a serial number that contains the search term or is an exact match.
perPageNoThe number of entries per page returned. Acceptable range is 3 - 1000. Default is 1000.
serialsNoOptional parameter to filter devices by one or more serial numbers. All returned devices will have a serial number that is an exact match.
networkIdsNoOptional parameter to filter devices by network.
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.
productTypesNoOptional parameter to filter devices by product type. Valid types are wireless, appliance, switch, systemsManager, camera, cellularGateway, sensor, wirelessController, campusGateway, and secureConnect.
sensorMetricsNoOptional parameter to filter devices by the metrics that they provide. Only applies to sensor devices.
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
tagsFilterTypeNoOptional 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.
sensorAlertProfileIdsNoOptional parameter to filter devices by the alert profiles that are bound to them. Only applies to sensor devices.
configurationUpdatedAfterNoFilter results by whether or not the device's configuration has been updated after the given timestamp

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 must carry the full burden of disclosing behavioral traits. It only mentions the scope (devices assigned to a network) but omits important behaviors like pagination, filtering capabilities, read-only nature, or any prerequisites. The extensive parameter list implies pagination and filtering, but these are not disclosed in the description.

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?

The description is a single, concise sentence that immediately states the tool's purpose. It contains no filler or redundant information, making it highly efficient and easy to parse.

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?

While the tool has 18 parameters and an output schema, the description itself is minimal. The schema and output schema carry most of the contextual detail. The description adds only the 'assigned to a network' scope. This is sufficient for basic understanding but lacks guidance on how to effectively use the many filters and pagination features, making it only minimally complete for a complex tool.

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 parameters are fully documented in the input schema. The description does not add any parameter-level meaning, but the schema already provides detailed descriptions for each of the 18 parameters. Thus, the baseline of 3 is appropriate.

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 the specific verb 'List' and identifies the resource as 'devices in an organization that have been assigned to a network.' This clearly distinguishes it from sibling tools that list networks, organizations, or licenses, making the tool's purpose unambiguous.

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 on when to use this tool versus alternatives such as getOrganizationNetworks or getOrganizationFirmwareUpgrades. The description states what it does but offers no contextual hints about preferable use cases, filtering scenarios, or exclusions.

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