---
title: "GraphQL query syntax check"
description: "Check GraphQL query shape and selected field names against pasted SDL. Review line-level errors locally without sending or executing the operation before use."
url: https://findutils.com/developers/graphql-playground/
category: developers
---

# GraphQL query syntax check

Check GraphQL query shape and selected field names against pasted SDL. Review line-level errors locally without sending or executing the operation before use.

**Use this tool:** [GraphQL query syntax check](https://findutils.com/developers/graphql-playground/)

## Programmatic access

- REST id `graphql-playground`: POST https://api.findutils.com/api/tools/graphql-playground/execute (reference: https://findutils.com/api/graphql-playground/)
- MCP tool `graphql_playground` on https://mcp.findutils.com (reference: https://findutils.com/mcp/graphql-playground/)

## Why this is a syntax check

This page checks balanced braces, brackets, parentheses, operation shape, and selected field names when the SDL defines those types. Errors include a line number. It does not execute the query or provide complete GraphQL validation. Text stays in your browser. Analytics or ads on the page may still load.

## GraphQL Check Tips

- Put each SDL field on its own line so the basic field checker can read it.
- Use this page for query shape checks, not for execution or full GraphQL validation.
- Check argument types, required arguments, variables, directives, and fragments with a full GraphQL implementation.
- Use the error sample to see how an unknown nested field is reported.
- Use the GraphQL Schema Validator when the SDL itself needs a schema-focused check.

## Frequently Asked Questions

### Does this run the query against a server?

No. FindUtils checks query shape and selected field names in your browser. It does not send the operation to a GraphQL endpoint.

### Is this a full GraphQL engine?

No. FindUtils provides a limited syntax and field-name check. It is not a complete GraphQL parser, validator, client, or execution engine.

### Does it support fragments?

Fragment support is limited and not a complete implementation. The checker can still report delimiter errors, but a passed result does not validate fragment rules.

### Can I paste an introspection result?

No. The field-name checker expects GraphQL SDL, not an introspection JSON result. Convert or obtain SDL before you use schema field checks.

### Is there a GraphQL schema validator too?

Yes. Use GraphQL Schema Validator for schema-focused checks. This query tool reads only a limited SDL field map.

### Which syntax errors does it find?

It finds unexpected or unclosed braces, brackets, and parentheses. It also reports selected unknown fields when supported SDL type information is available.

### Does it validate field arguments and variable types?

No. It reads past variable declarations and balanced argument groups. It does not validate argument names, required values, or variable types.

### Does it validate the SDL itself?

No. It reads a limited type and field map from SDL. Use a full schema validator for SDL grammar and complete type-system rules.

### Why should SDL fields use separate lines?

The basic SDL reader recognizes field definitions line by line. A compact one-line type can prevent field-name checks while the query shape check still runs.

### Does a passed check mean the query will run?

No. A passed result does not test a server, resolvers, permissions, variable values, arguments, directives, or complete fragment behavior. Run complete validation in the target GraphQL stack.

## Related Tools

- [GraphQL Schema Validator](https://findutils.com/developers/graphql-schema-validator/)
- [GraphQL to TypeScript](https://findutils.com/developers/graphql-to-typescript/)
- [JSON Formatter](https://findutils.com/developers/json-formatter/)