Drupal Code Query

List projects by filters

list_projects

Read-onlyIdempotent

List drupal.org projects after filters, largest install base first, paged. Examples: "top modules without an 11.4 branch", "themes over 10k installs without security coverage". One project: project_profile. Its pending records: project_upgrade_report.

Filters combine: type, min_installs, security (covered, not-covered, revoked), core_minor (+ missing), era (d8plus, pre_d8). All apply to count and rows.
core_minor reads the composer constraint of the newest release on each development branch. A minor counts when any patch of it satisfies the constraint. An unreleased tip change is not seen. missing=true keeps projects with no branch declaring it: the upgrade gap list.
Row: machine_name, title, type, installs, security, status, dev_branches (branch, installs, core_minors, era), latest_release. count: projects. next_offset is absent on the last page.

Input Schema

TableJSON Schema

Name	Required	Description
`era`	No	Filter: d8plus (Drupal 8+ code) or pre_d8, on any development branch.
`type`	No	Filter: project_module, project_theme, project_distribution, project_general, project_theme_engine, project_translation.
`limit`	No	Projects per page, 1 to 100 (default 50).
`offset`	No	Skip this many projects in the same ranked order. Pass the previous page's next_offset.
`missing`	No	Invert core_minor: keep projects whose development branches do not declare it.
`security`	No	Filter: security advisory coverage: covered, not-covered, revoked.
`core_minor`	No	Filter: a core minor in 11.4.x form. Keeps projects where the newest release on some development branch declares support for it. With missing=true, keeps projects with no such branch.
`min_installs`	No	Filter: reported install base at or above this.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed3 schema fields changedSep 2, 2026

changedInput schema / properties / core_minor / description

Previous value: -"Filter: a core minor in 11.4.x form that the newest release on some development branch declares support for (composer constraint from drupal.org); with missing=true, projects with NO such branch."New value: +"Filter: a core minor in 11.4.x form. Keeps projects where the newest release on some development branch declares support for it. With missing=true, keeps projects with no such branch."

changedInput schema / properties / offset / description

Previous value: -"Skip this many projects in the same ranked order; pass the previous page's next_offset."New value: +"Skip this many projects in the same ranked order. Pass the previous page's next_offset."

changedInput schema / properties / security / description

Previous value: -"Filter: security advisory coverage — covered, not-covered, revoked."New value: +"Filter: security advisory coverage: covered, not-covered, revoked."

Changed1 schema field changedAug 19, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "count": {
-      "type": "integer"
-    },
-    "next_offset": {
-      "type": "integer"
-    },
-    "ranked_by": {
-      "type": "string"
-    },
-    "rows": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "dev_branches": {
-            "items": {
-              "additionalProperties": false,
-              "properties": {
-                "branch": {
-                  "type": "string"
-                },
-                "core_minors": {
-                  "items": {
-                    "type": "string"
-                  },
-                  "type": [
-                    "null",
-                    "array"
-                  ]
-                },
-                "era": {
-                  "type": "string"
-                },
-                "installs": {
-                  "type": "integer"
-                }
-              },
-              "required": [
-                "branch",
-                "installs",
-                "core_minors"
-              ],
-              "type": "object"
-            },
-            "type": [
-              "null",
-              "array"
-            ]
-          },
-          "installs": {
-            "type": "integer"
-          },
-          "latest_release": {
-            "additionalProperties": false,
-            "properties": {
-              "core_compatibility": {
-                "type": "string"
-              },
-              "date": {
-                "type": "string"
-              },
-              "security": {
-                "type": "boolean"
-              },
-              "status": {
-                "type": "string"
-              },
-              "version": {
-                "type": "string"
-              }
-            },
-            "required": [
-              "version",
-              "security"
-            ],
-            "type": [
-              "null",
-              "object"
-            ]
-          },
-          "machine_name": {
-            "type": "string"
-          },
-          "security": {
-            "type": "string"
-          },
-          "status": {
-            "type": "string"
-          },
-          "title": {
-            "type": "string"
-          },
-          "type": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "machine_name",
-          "installs",
-          "dev_branches"
-        ],
-        "type": "object"
-      },
-      "type": [
-        "null",
-        "array"
-      ]
-    }
-  },
-  "required": [
-    "count",
-    "rows",
-    "ranked_by"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedAug 19, 2026

changedInput schema / properties / core_minor / description

Previous value: -"Filter: a core minor in 11.4.x form that some development branch declares support for; with missing=true, projects with NO such branch."New value: +"Filter: a core minor in 11.4.x form that the newest release on some development branch declares support for (composer constraint from drupal.org); with missing=true, projects with NO such branch."

AddedAug 19, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses ordering by install base, paging via next_offset, filter combination semantics, and the exact core_minor algorithm (newest release on each development branch, patch-level constraint matching, unreleased tip changes not seen). This is substantial behavioral detail and does not contradict the annotations.

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 information-dense but not padded; purpose, examples, filtering semantics, and return shape are each covered in compact, organized bullets. Front-loading the core purpose and ordering makes the tool easy to understand quickly.

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 no output schema, the description compensates by specifying the row fields, count, and next_offset behavior. Combined with full parameter documentation and annotations covering safety guarantees, an agent has everything it needs to call and interpret the tool correctly.

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?

The schema already documents all parameters at 100% coverage, so the baseline is 3. The description adds meaningful semantics beyond the schema, especially for core_minor and missing: it explains how constraints are read, what 'missing' means for upgrade gaps, and that all filters apply to both count and rows.

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 states a specific action and resource: 'List drupal.org projects after filters' with deterministic ordering. It gives concrete example queries and even points to sibling tools for the single-project and pending-record cases, so an agent can distinguish it from project_profile and project_upgrade_report.

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?

The examples ('top modules without an 11.4 branch', 'themes over 10k installs without security coverage') make the intended use concrete, and the note that project_profile and project_upgrade_report cover one-project and pending-record needs provides some alternative routing. It could be more explicit about when to choose query_dataset or search_code instead, but the context is clear.

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

All Drupal Code Query tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0

Disambiguation4/5

Tools cluster into related families (change records, symbol usage, patch checks), but descriptions and cross-references clearly separate list vs detail vs diff operations. Some adjacent tools like lookup_core_symbol and list_symbol_users require careful reading, yet their purposes are distinct enough for an agent to select correctly.

Naming Consistency4/5

Most tools follow a clear snake_case verb_noun pattern: list_*, get_*, lookup_*, query_, scan_, search_, reroll_, describe_. A few names like project_profile, subsystem_coupling, and what_changed deviate from verb_noun but remain consistent in style and readable.

Tool Count4/5

At 16 tools, the set is slightly above the typical well-scoped range, but the domain is broad: patch lifecycle, composer scanning, symbol lookup, change records, project profiles, dataset queries, and code search. Each tool covers a distinct query surface, so none feels redundant.

Completeness5/5

The toolkit covers the full read-only analysis lifecycle: scanning composer constraints, checking and re-rolling patches, exploring datasets, looking up core symbols and their users, listing change records, profiling projects, and assessing upgrade readiness. No obvious dead ends or missing operations for its stated purpose.

Resources

Need Help?