GraphQL Mutation Design Principles: Explicit Naming, Single Input Object, and Nested Structures

When designing GraphQL Mutations, it is recommended to follow three core principles. First, explicit naming. RPC-style Mutations that reveal specific intent, such as sendPasswordResetEmail, leverage the benefits of the type system and are advantageous for UI development and security compared to generic Mutations. Second, the use of a single input object. A Mutation should accept only one argument, a non-null unique input object type named input, which simplifies variable handling on the client side. Third, the utilization of nested structures. Designing input objects and return values (Payloads) as nested custom object types reduces the burden of schema changes and maintains API version compatibility when adding metadata fields like clientMutationId or error information, or when deprecating existing fields.